From: Mike Stump <mrs@apple.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: howarth@bromo.msbb.uc.edu (Jack Howarth),
gcc@gcc.gnu.org, schwab@suse.de
Subject: Re: strange error on gcc 4.1.0
Date: Sun, 31 Jul 2005 04:44:00 -0000 [thread overview]
Message-ID: <C6CF2E28-017D-11DA-BCD4-003065BDF310@apple.com> (raw)
In-Reply-To: <f4f0e60bee65de20d84b218c77240c81@physics.uc.edu>
On Saturday, July 30, 2005, at 09:09 AM, Andrew Pinski wrote:
> But I don't know what happened to it or came up from the discussion.
Looks like no response to Geoff's last comment. If someone wants to
address his stated concerns and resubmit it... otherwise, -Wl,-bundle
should do the trick.
next prev parent reply other threads:[~2005-07-31 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 15:55 Jack Howarth
2005-07-30 16:09 ` Andrew Pinski
2005-07-31 4:44 ` Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 16:22 Jack Howarth
2005-07-30 16:15 Jack Howarth
2005-07-30 13:42 Jack Howarth
2005-07-30 15:18 ` Andrew Pinski
2005-07-30 8:47 Jack Howarth
2005-07-30 9:50 ` Andreas Schwab
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=C6CF2E28-017D-11DA-BCD4-003065BDF310@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.msbb.uc.edu \
--cc=pinskia@physics.uc.edu \
--cc=schwab@suse.de \
/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).