public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ianmcc at physik dot rwth-aachen dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/24298] Libstdc++ uses anonymous enums, causing failures due to DR488 Date: Mon, 10 Oct 2005 16:36:00 -0000 [thread overview] Message-ID: <20051010163614.12169.qmail@sourceware.org> (raw) In-Reply-To: <bug-24298-11498@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from ianmcc at physik dot rwth-aachen dot de 2005-10-10 16:36 ------- See also bug #[20589] -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24298
next prev parent reply other threads:[~2005-10-10 16:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-10 16:28 [Bug libstdc++/24298] New: " ianmcc at physik dot rwth-aachen dot de 2005-10-10 16:29 ` [Bug libstdc++/24298] " ianmcc at physik dot rwth-aachen dot de 2005-10-10 16:36 ` ianmcc at physik dot rwth-aachen dot de [this message] 2005-10-10 16:39 ` pinskia at gcc dot gnu dot org 2005-10-10 16:44 ` pinskia at gcc dot gnu dot org 2005-10-10 16:50 ` ianmcc at physik dot rwth-aachen dot de 2005-10-10 17:09 ` pinskia 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=20051010163614.12169.qmail@sourceware.org \ --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).