From: David Edelsohn <dje@watson.ibm.com>
To: Matt Austern <austern@apple.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
gcc@gcc.gnu.org, law@redhat.com
Subject: Re: speedup collect2 (by not using it)
Date: Fri, 23 May 2003 02:46:00 -0000 [thread overview]
Message-ID: <200305230059.UAA27450@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Matt Austern <austern@apple.com> of "Thu, 22 May 2003 15:31:05 PDT." <132E6AB0-8CA5-11D7-AC1D-00039390D9E0@apple.com>
>>>>> Matt Austern writes:
Matt> But in any case, isn't this a bit tangential to the question Mike
Matt> asked? He asked what happens on systems where USE_COLLECT2
Matt> *isn't* defined, and you're talking about systems where it is (or at
Matt> least was) defined.
Mike asked about AIX and systems with ctor requirements like AIX.
Those system define use_collect2=yes.
David
prev parent reply other threads:[~2003-05-23 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 22:31 John David Anglin
2003-05-22 22:35 ` Matt Austern
2003-05-23 0:29 ` John David Anglin
2003-05-23 2:46 ` David Edelsohn [this message]
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=200305230059.UAA27450@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=austern@apple.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).