From: Andrew Pinski <pinskia@physics.uc.edu>
To: howarth@bromo.msbb.uc.edu (Jack Howarth)
Cc: gcc@gcc.gnu.org, schwab@suse.de
Subject: Re: strange error on gcc 4.1.0
Date: Sat, 30 Jul 2005 16:09:00 -0000 [thread overview]
Message-ID: <f4f0e60bee65de20d84b218c77240c81@physics.uc.edu> (raw)
In-Reply-To: <20050730155223.F2B211DC154@bromo.msbb.uc.edu>
On Jul 30, 2005, at 11:52 AM, Jack Howarth wrote:
> I can't find a patch either using google but I did find the
> following
> posting which describes the problem and a workaround...
>
> http://www.mail-archive.com/fink-devel@lists.sourceforge.net/
> msg10604.html
I finally found the patch:
http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00655.html
http://gcc.gnu.org/ml/gcc-patches/2002-10/msg01961.html
But I don't know what happened to it or came up from the discussion.
-- Pinski
next prev parent reply other threads:[~2005-07-30 16:09 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 [this message]
2005-07-31 4:44 ` Mike Stump
-- 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=f4f0e60bee65de20d84b218c77240c81@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.msbb.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).