From: Nathan Froyd via cfe-dev <cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org>
To: "Ludovic Courtès" <ludo-mXXj517/zsQ@public.gmane.org>
Cc: Guix-devel <guix-devel-mXXj517/zsQ@public.gmane.org>,
nix-dev-rGrgPyRx506NN8uzcEdRPYRWq/SkRNHw@public.gmane.org,
cfe-dev-NBbBogny7ofFcdTEL8lfRQ@public.gmane.org,
gcc-/MQLu3FmUzdAfugRpC6u6w@public.gmane.org
Subject: Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment
Date: Tue, 18 Oct 2016 09:46:43 -0400 [thread overview]
Message-ID: <CAGepuV+VpTJfu=RUtEioxx47QgKDCvkeN40wisGt9aceXj1mDg@mail.gmail.com> (raw)
In-Reply-To: <8737jtlsnw.fsf-mXXj517/zsQ@public.gmane.org>
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
next prev parent reply other threads:[~2016-10-18 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r37gp8dt.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me>
2016-10-18 9:25 ` [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment Ludovic Courtès
[not found] ` <87vawqm2je.fsf-mXXj517/zsQ@public.gmane.org>
2016-10-18 11:03 ` Shea Levy via cfe-dev
2016-10-18 11:19 ` Shea Levy
2016-10-18 12:59 ` Ludovic Courtès
[not found] ` <8737jtlsnw.fsf-mXXj517/zsQ@public.gmane.org>
2016-10-18 13:46 ` Nathan Froyd via cfe-dev [this message]
[not found] ` <CAGepuV+VpTJfu=RUtEioxx47QgKDCvkeN40wisGt9aceXj1mDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-27 17:11 ` Will Dietz via cfe-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGepuV+VpTJfu=RUtEioxx47QgKDCvkeN40wisGt9aceXj1mDg@mail.gmail.com' \
--to=cfe-dev-nbbbogny7offcdtel8lfrq@public.gmane.org \
--cc=gcc-/MQLu3FmUzdAfugRpC6u6w@public.gmane.org \
--cc=guix-devel-mXXj517/zsQ@public.gmane.org \
--cc=ludo-mXXj517/zsQ@public.gmane.org \
--cc=nfroyd-4eJtQOnFJqFBDgjK7y7TUQ@public.gmane.org \
--cc=nix-dev-rGrgPyRx506NN8uzcEdRPYRWq/SkRNHw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).