public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.frey at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/56468] Clang exposes bug with unexpected forward-declaration of type_info Date: Thu, 28 Feb 2013 16:15:00 -0000 [thread overview] Message-ID: <bug-56468-4-GaDb5yJb3K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56468-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56468 --- Comment #4 from Daniel Frey <d.frey at gmx dot de> 2013-02-28 16:14:41 UTC --- (In reply to comment #1) I think the first line you added is enough, as evidenced by my "fix" referenced in the Stack Overflow discussion (see link above). But the second line won't hurt either.
next prev parent reply other threads:[~2013-02-28 16:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-26 22:50 [Bug libstdc++/56468] New: " d.frey at gmx dot de 2013-02-26 23:22 ` [Bug libstdc++/56468] " redi at gcc dot gnu.org 2013-02-27 7:36 ` jakub at gcc dot gnu.org 2013-02-27 9:34 ` redi at gcc dot gnu.org 2013-02-28 16:15 ` d.frey at gmx dot de [this message] 2013-03-16 20:02 ` redi at gcc dot gnu.org 2013-03-16 20:23 ` redi at gcc dot gnu.org 2013-03-16 20:24 ` redi at gcc dot gnu.org 2013-03-16 23:46 ` steven at gcc dot gnu.org 2013-03-17 11:36 ` jakub at gcc dot gnu.org 2013-03-17 14:11 ` redi at gcc dot gnu.org 2013-03-17 14:12 ` redi 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-56468-4-GaDb5yJb3K@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: linkBe 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).