public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/7385] [3.3/3.4 Regression] g++ problems with enum and __attribute__
Date: Tue, 05 Aug 2003 20:25:00 -0000 [thread overview]
Message-ID: <20030805202513.23782.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020723051601.7385.gusti@pallas.dk>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7385
janis187 at us dot ibm dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com
------- Additional Comments From janis187 at us dot ibm dot com 2003-08-05 20:25 -------
The regression in PR 7385 was introduced or exposed by this patch:
--- gcc/gcc/cp/ChangeLog ---
2002-04-30 Jason Merrill <jason@redhat.com>
* decl.c (grokdeclarator): Don't override TYPE_NAME of an
anonymous class with a typedef if there are attributes.
The regression hunt took place on i686-pc-linux-gnu using the submitter's
test case. Like many other recent hunts, it started with the dates
identified by Andrew Pinski using Phil's regression hunter.
next prev parent reply other threads:[~2003-08-05 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020723051601.7385.gusti@pallas.dk>
2003-07-17 2:53 ` [Bug c++/7385] " pinskia at physics dot uc dot edu
2003-07-17 7:03 ` mark at codesourcery dot com
2003-07-17 12:48 ` pinskia at physics dot uc dot edu
2003-07-22 18:29 ` pinskia at physics dot uc dot edu
2003-07-29 18:00 ` [Bug c++/7385] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu
2003-08-05 20:25 ` janis187 at us dot ibm dot com [this message]
2003-08-09 2:02 ` pinskia at gcc dot gnu dot org
2003-08-29 20:40 ` jason at gcc dot gnu dot org
2003-08-29 20:48 ` jason at gcc dot gnu dot org
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=20030805202513.23782.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).