public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55877] [4.6 Regression] Anon visibility issues
Date: Mon, 07 Jan 2013 16:44:00 -0000 [thread overview]
Message-ID: <bug-55877-4-EqRtrM6rbt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55877-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55877
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> 2013-01-07 16:43:55 UTC ---
(In reply to comment #4)
> BTW, what about:
> typedef struct {
> typedef enum { X, Y } A;
> typedef struct { } B;
> struct C {
> static void fn1 (B) { }
> static void fn2 (C) { }
> };
> } D;
Hmm, yes, that's still a regression from 4.4.
next prev parent reply other threads:[~2013-01-07 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 15:14 [Bug c++/55877] New: [4.6/4.7/4.8 " jakub at gcc dot gnu.org
2013-01-04 15:24 ` [Bug c++/55877] " jason at gcc dot gnu.org
2013-01-04 15:28 ` jakub at gcc dot gnu.org
2013-01-04 16:51 ` jason at gcc dot gnu.org
2013-01-04 16:51 ` jason at gcc dot gnu.org
2013-01-04 16:58 ` [Bug c++/55877] [4.6 " jason at gcc dot gnu.org
2013-01-04 17:08 ` jakub at gcc dot gnu.org
2013-01-04 20:32 ` jason at gcc dot gnu.org
2013-01-07 16:44 ` jason at gcc dot gnu.org [this message]
2013-02-08 15:06 ` [Bug c++/55877] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-04-12 15:15 ` [Bug c++/55877] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-01-23 10:33 ` paolo.carlini at oracle dot com
2014-01-23 10:36 ` jakub at gcc dot gnu.org
2014-02-25 21:19 ` jason at gcc dot gnu.org
2014-02-25 21:19 ` jason at gcc dot gnu.org
2014-02-27 16:21 ` jason at gcc dot gnu.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=bug-55877-4-EqRtrM6rbt@http.gcc.gnu.org/bugzilla/ \
--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).