public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: Sven Gohlke <sven@clio.in-berlin.de>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: Maybe a bug in G++
Date: Sun, 18 Jul 2004 18:18:00 -0000 [thread overview]
Message-ID: <CB5CB9BB-D8E6-11D8-B524-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <200407181930.04707.sven@clio.in-berlin.de>
On Jul 18, 2004, at 10:30 AM, Sven Gohlke wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I think I have found an identifier lookup bug in g++ (GCC) 3.3.3
> (Debian
> 20040422). Attached are two files, one which compiles and one which
> doesn't
> though I think that it should compile.
Yes this is a bug in 3.3.x and before but it has been fixed in 3.4.0
and newer.
Thanks,
Andrew Pinski
prev parent reply other threads:[~2004-07-18 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 17:40 Sven Gohlke
2004-07-18 18:18 ` Andrew Pinski [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=CB5CB9BB-D8E6-11D8-B524-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc-bugs@gcc.gnu.org \
--cc=sven@clio.in-berlin.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).