[prev in list] [next in list] [prev in thread] [next in thread]
List: cfe-dev
Subject: Re: [cfe-dev] [RFC] Reliable compiler specification setting (at least include/lib dirs) through the
From: Will Dietz via cfe-dev <cfe-dev () lists ! llvm ! org>
Date: 2016-10-27 17:11:59
Message-ID: CAKGWAO-s3M77U3J8RNL8JwFuuhQd0R7ud1r4-v-mwV+wnwzcew () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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=13246
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@lists.llvm.org> wrote:
> On Tue, Oct 18, 2016 at 8:59 AM, Ludovic Courtès via cfe-dev
> <cfe-dev@lists.llvm.org> wrote:
> > Shea Levy <shea@shealevy.com> skribis:
> >
> >> Your patches look good! My biggest concern is how the ld wrapper behaves
> >> in the presence of response files. Have you tested that?
> >
> > It surely doesn't (yet?).
> >
> > However, GCC does not pass "@file" arguments when it invokes ‘ld', and
> > the bug report you mentioned ¹ talks about GHC invoking ‘gcc', not ‘ld',
> > so I guess it's 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@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
[Attachment #5 (text/html)]
<div dir="ltr">Yes! I'm very interested in this as well!<div><br></div><div>One \
piece of information to add: it might be worth investigating something</div><div>more \
general like the configuration files used by ELLCC in controlling their \
cross-compilers.</div><div><br></div><div>This was somewhat recently discussed \
here:</div><div><br></div><div><a \
href="http://lists.llvm.org/pipermail/llvm-dev/2015-July/087907.html">http://lists.llv \
m.org/pipermail/llvm-dev/2015-July/087907.html</a><br></div><div><br></div><div>And \
looks like the most recent description of it is here:</div><div><br></div><div><a \
href="http://ellcc.org/blog/?p=13246">http://ellcc.org/blog/?p=13246</a><br></div><div><br></div><div>This \
would be rather useful in Nix for creating cross-compilers as \
well.</div><div><br></div><div>AFAIK this isn't immediately suited to your needs \
but I think that it's the right direction to go</div><div>and it'd be ideal \
to support both use-cases if we are talking about upstream \
support.</div><div><br></div><div>~Will</div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr">On Tue, Oct 18, 2016 at 8:46 AM Nathan Froyd via \
cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Oct 18, 2016 at 8:59 AM, \
Ludovic Courtès via cfe-dev<br class="gmail_msg"> <<a \
href="mailto:cfe-dev@lists.llvm.org" class="gmail_msg" \
target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br class="gmail_msg"> > Shea \
Levy <<a href="mailto:shea@shealevy.com" class="gmail_msg" \
target="_blank">shea@shealevy.com</a>> skribis:<br class="gmail_msg"> ><br \
class="gmail_msg"> >> Your patches look good! My biggest concern is how the ld \
wrapper behaves<br class="gmail_msg"> >> in the presence of response files. \
Have you tested that?<br class="gmail_msg"> ><br class="gmail_msg">
> It surely doesn't (yet?).<br class="gmail_msg">
><br class="gmail_msg">
> However, GCC does not pass "@file" arguments when it invokes ‘ld', and<br \
class="gmail_msg"> > the bug report you mentioned ¹ talks about GHC invoking \
‘gcc', not ‘ld',<br class="gmail_msg"> > so I guess it's fine to ignore \
response files in the ld wrapper.<br class="gmail_msg"> <br class="gmail_msg">
GCC will pass response files to ld when response files were used in<br \
class="gmail_msg"> the invocation of GCC.<br class="gmail_msg">
<br class="gmail_msg">
-Nathan<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
cfe-dev mailing list<br class="gmail_msg">
<a href="mailto:cfe-dev@lists.llvm.org" class="gmail_msg" \
target="_blank">cfe-dev@lists.llvm.org</a><br class="gmail_msg"> <a \
href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" \
class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br \
class="gmail_msg"> </blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
cfe-dev mailing list
cfe-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic