From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Dietz via cfe-dev Subject: Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment Date: Thu, 27 Oct 2016 17:11:59 +0000 Message-ID: References: <87r37gp8dt.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> <87vawqm2je.fsf@gnu.org> <87eg3d7vle.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> <8737jtlsnw.fsf@gnu.org> Reply-To: Will Dietz Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4039144441369022499==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cfe-dev-bounces-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org Sender: "cfe-dev" To: Nathan Froyd , =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix-devel , gcc-/MQLu3FmUzdAfugRpC6u6w@public.gmane.org, nix-dev-rGrgPyRx506NN8uzcEdRPYRWq/SkRNHw@public.gmane.org, cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org List-Id: guix-devel.gnu.org --===============4039144441369022499== Content-Type: multipart/alternative; boundary=001a1140109490a02d053fdbd78c --001a1140109490a02d053fdbd78c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes! I'm very interested in this as well! One piece of information to add: it might be worth investigating something more general like the configuration files used by ELLCC in controlling their cross-compilers. This was somewhat recently discussed here: http://lists.llvm.org/pipermail/llvm-dev/2015-July/087907.html And looks like the most recent description of it is here: http://ellcc.org/blog/?p=3D13246 This would be rather useful in Nix for creating cross-compilers as well. AFAIK this isn't immediately suited to your needs but I think that it's the right direction to go and it'd be ideal to support both use-cases if we are talking about upstream support. ~Will On Tue, Oct 18, 2016 at 8:46 AM Nathan Froyd via cfe-dev < cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org> wrote: > On Tue, Oct 18, 2016 at 8:59 AM, Ludovic Court=C3=A8s via cfe-dev > wrote: > > Shea Levy skribis: > > > >> Your patches look good! My biggest concern is how the ld wrapper behav= es > >> in the presence of response files. Have you tested that? > > > > It surely doesn=E2=80=99t (yet?). > > > > However, GCC does not pass =E2=80=9C@file=E2=80=9D arguments when it in= vokes =E2=80=98ld=E2=80=99, and > > the bug report you mentioned=C2=B9 talks about GHC invoking =E2=80=98gc= c=E2=80=99, not =E2=80=98ld=E2=80=99, > > so I guess it=E2=80=99s fine to ignore response files in the ld wrapper= . > > GCC will pass response files to ld when response files were used in > the invocation of GCC. > > -Nathan > _______________________________________________ > cfe-dev mailing list > cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > --001a1140109490a02d053fdbd78c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes! I'm very interested in this as well!

One piece of information to add: it might be worth investigating som= ething
more general like the configuration files used by ELLCC in= controlling their cross-compilers.

This was somew= hat recently discussed here:


= And looks like the most recent description of it is here:


This would be rather useful in = Nix for creating cross-compilers as well.

AFAIK th= is isn't immediately suited to your needs but I think that it's the= right direction to go
and it'd be ideal to support both use-= cases if we are talking about upstream support.

~W= ill


On Tue, Oct 18, 2016 at 8:46 AM Nathan Froyd via cfe-dev <cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org> wrote:
On Tue, Oct 18, 2016 at 8:59 AM, Ludovic = Court=C3=A8s via cfe-dev
<cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org> wrote:
> Shea Levy <shea-yfkUTty7RcRWk0Htik3J/w@public.gmane.org> skribis:
>
>> Your patches look good! My biggest concern is how the ld wrapper b= ehaves
>> in the presence of response files. Have you tested that?
>
> It surely doesn=E2=80=99t (yet?).
>
> However, GCC does not pass =E2=80=9C@file=E2=80=9D arguments when it i= nvokes =E2=80=98ld=E2=80=99, and
> the bug report you mentioned=C2=B9 talks about GHC invoking =E2=80=98g= cc=E2=80=99, not =E2=80=98ld=E2=80=99,
> so I guess it=E2=80=99s fine to ignore response files in the ld wrappe= r.

GCC will pass response files to ld when response files were used in
the invocation of GCC.

-Nathan
_______________________________________________
cfe-dev mailing list
cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org
http://lists.llvm.org/cgi-= bin/mailman/listinfo/cfe-dev
--001a1140109490a02d053fdbd78c-- --===============4039144441369022499== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KY2ZlLWRldiBt YWlsaW5nIGxpc3QKY2ZlLWRldkBsaXN0cy5sbHZtLm9yZwpodHRwOi8vbGlzdHMubGx2bS5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2NmZS1kZXYK --===============4039144441369022499==--