From: Ian Lance Taylor <iant@google.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Rafael Espindola <espindola@google.com>, gcc@gcc.gnu.org
Subject: Re: -use-linker-plugin passed to ld
Date: Fri, 23 Oct 2009 19:07:00 -0000 [thread overview]
Message-ID: <mcrtyxqueyr.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <571f6b510910231135y2e5be00eq2247b3878b7cccbd@mail.gmail.com> (Steven Bosscher's message of "Fri\, 23 Oct 2009 20\:35\:38 +0200")
Steven Bosscher <stevenb.gcc@gmail.com> writes:
> On Fri, Oct 23, 2009 at 8:21 PM, Ian Lance Taylor <iant@google.com> wrote:
>> Rafael Espindola <espindola@google.com> writes:
>>
>>> 2009-10-23 Rafael Avila de Espindola <espindola@google.com>
>>>
>>> * gcc.c (LINK_COMMAND_SPEC): Remove -use-linker-plugin from the command
>>> line.
>>
>> This is OK if it passes bootstrap and if nobody objects in 24 hours.
>
>
> I was just wondering why this is not a -f* flag, e.g. -fuse-linker-plugin?
I thought about that too, but a -f flag would be passed to the
middle-end, where it does not make any sense. We could make it a -f
flag anyhow, of course, and just explicitly ignore it in the
middle-end.
Any opinions on the best user interface for this?
Ian
next prev parent reply other threads:[~2009-10-23 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 15:02 Ian Lance Taylor
2009-10-23 15:45 ` Rafael Espindola
2009-10-23 16:49 ` Rafael Espindola
2009-10-23 18:45 ` Ian Lance Taylor
2009-10-23 19:00 ` Steven Bosscher
2009-10-23 19:07 ` Ian Lance Taylor [this message]
2009-10-24 4:26 ` Rafael Espindola
2009-10-26 23:27 ` Hans-Peter Nilsson
2009-10-27 6:09 ` Daniel Jacobowitz
2009-10-27 15:55 ` Rafael Espindola
2009-10-27 16:45 ` Andreas Schwab
2009-10-27 17:01 ` Ian Lance Taylor
2009-10-27 17:22 ` Rafael Espindola
2009-10-27 17:24 ` Rafael Espindola
2009-10-27 19:50 ` Ian Lance Taylor
2009-10-27 18:23 ` Andrew Pinski
2009-10-27 18:54 ` Rafael Espindola
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcrtyxqueyr.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=espindola@google.com \
--cc=gcc@gcc.gnu.org \
--cc=stevenb.gcc@gmail.com \
/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.
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).