From: Jon Grant <jg@jguk.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Long paths with ../../../../ throughout
Date: Mon, 04 Jul 2011 20:14:00 -0000 [thread overview]
Message-ID: <4E121F0F.8000904@jguk.org> (raw)
In-Reply-To: <mcr39iof0px.fsf@coign.corp.google.com>
Ian Lance Taylor wrote, On 03/07/11 05:27:
> Jon Grant<jg@jguk.org> writes:
[.]
>> Another reply for this old thread. I wondered, if collect2 is
>> possibly not needed in normal use on GNU/Linux, could GCC be
>> configured to call ld directly in those cases to save launching
>> another binary.
>
> collect2 is needed if you use -frepo or -flto.
Hi Ian.
Not sure how easy this is, but could those options simply be checked to
determine if the linker could be called directly? Would save launching
collect2 then, to speed up builds a bit!
Best regards, Jon
next prev parent reply other threads:[~2011-07-04 20:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 17:34 Jon Grant
2010-01-19 17:35 ` Jon Grant
2010-01-19 17:40 ` Jon Grant
2010-01-19 18:18 ` Ian Lance Taylor
2010-01-23 16:26 ` Jon Grant
2010-01-25 18:44 ` Ian Lance Taylor
2010-02-02 22:38 ` Jon
2010-02-02 22:47 ` Ian Lance Taylor
2010-02-03 21:56 ` Jon
2010-02-03 22:46 ` Jon
2010-02-04 1:01 ` Ian Lance Taylor
2010-02-05 20:38 ` Jon
2010-02-20 7:57 ` Jon
2010-02-20 11:48 ` Joseph S. Myers
2010-02-21 0:43 ` Jon
2010-02-22 3:26 ` Ian Lance Taylor
2010-03-14 6:25 ` Jon
2010-03-15 7:35 ` Ian Lance Taylor
2010-04-24 22:47 ` Jon
2010-04-24 22:54 ` Manuel López-Ibáñez
2010-04-25 18:06 ` Ian Lance Taylor
2010-04-25 21:15 ` Manuel López-Ibáñez
2010-04-25 21:23 ` Jon
2010-04-25 21:39 ` Manuel López-Ibáñez
2010-04-26 23:57 ` Jon
2010-04-27 0:59 ` Dave Korn
2010-04-27 7:50 ` Manuel López-Ibáñez
2010-04-27 16:02 ` Dave Korn
2010-04-26 4:13 ` Ian Lance Taylor
2011-07-02 22:04 ` Jon Grant
2011-07-03 4:27 ` Ian Lance Taylor
2011-07-03 7:33 ` Richard Guenther
2011-07-04 20:14 ` Jon Grant [this message]
2011-07-05 18:37 ` Ian Lance Taylor
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=4E121F0F.8000904@jguk.org \
--to=jg@jguk.org \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).