From: Mark Kettenis <kettenis@chello.nl>
To: mec.gnu@mindspring.com
Cc: mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Deal with GCC bug on 64-bit SPARC
Date: Sat, 03 Jan 2004 23:34:00 -0000 [thread overview]
Message-ID: <200401032334.i03NYC2r000467@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040103230641.6D46E4B35A@berman.michael-chastain.com> (mec.gnu@mindspring.com)
Date: Sat, 3 Jan 2004 18:06:41 -0500 (EST)
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> I've seen this with GCC 3.3.2, GCC 3.3.3-ish and GCC 3.4. But I bet
> older versions have this problem too.
That's what I'd like to see in the source code. So that four years
from now, when we're worrying about gcc 4.1, we know that it's an
old comment and not a current comment.
Good point. I mentioned GCC 3.3.2 since that's the latest official
release. I've verified that it shows the problem. Better not mention
GCC 3.3.3 or GCC 3.4, since the bugs still might be fixed before those
are released ;-).
Mark
next prev parent reply other threads:[~2004-01-03 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 23:06 Michael Elizabeth Chastain
2004-01-03 23:34 ` Mark Kettenis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-03 22:47 Michael Elizabeth Chastain
2004-01-03 23:00 ` Mark Kettenis
2004-01-03 20:46 Mark Kettenis
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=200401032334.i03NYC2r000467@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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