public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/40224] [4.3/4.4/4.5 regression] g++ Accepting invalid code Date: Tue, 25 Aug 2009 15:52:00 -0000 [thread overview] Message-ID: <20090825154934.32447.qmail@sourceware.org> (raw) In-Reply-To: <bug-40224-17190@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from bangerth at gmail dot com 2009-08-25 15:49 ------- Confirmed. -- bangerth at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bangerth at gmail dot com Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |accepts-invalid Last reconfirmed|0000-00-00 00:00:00 |2009-08-25 15:49:33 date| | Summary|g++ Accepting invalid code |[4.3/4.4/4.5 regression] g++ | |Accepting invalid code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40224
next prev parent reply other threads:[~2009-08-25 15:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-22 14:57 [Bug c++/40224] New: g++ Accepting wrong code sergei_lus at yahoo dot com 2009-08-25 15:52 ` bangerth at gmail dot com [this message] 2009-08-25 15:52 ` [Bug c++/40224] [4.3/4.4/4.5 regression] g++ Accepting invalid code jsm28 at gcc dot gnu dot org 2009-08-31 16:46 ` jakub 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=20090825154934.32447.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).