public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43680] G++ is too aggressive in optimizing away bounds checking with enums Date: Wed, 07 Apr 2010 21:56:00 -0000 [thread overview] Message-ID: <20100407215601.27108.qmail@sourceware.org> (raw) In-Reply-To: <bug-43680-114@http.gcc.gnu.org/bugzilla/> -- jason at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Known to fail| |4.3.5 4.4.3 4.5.0 Last reconfirmed|2010-04-07 21:51:39 |2010-04-07 21:56:00 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43680
next prev parent reply other threads:[~2010-04-07 21:56 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-07 21:51 [Bug c++/43680] New: " jason at gcc dot gnu dot org 2010-04-07 21:52 ` [Bug c++/43680] " jason at gcc dot gnu dot org 2010-04-07 21:56 ` jason at gcc dot gnu dot org [this message] 2010-04-07 23:16 ` bangerth at gmail dot com 2010-04-08 2:58 ` jason at gcc dot gnu dot org 2010-04-08 3:18 ` bangerth at math dot tamu dot edu 2010-04-08 5:19 ` jason at gcc dot gnu dot org 2010-04-08 8:40 ` rguenth at gcc dot gnu dot org 2010-04-08 8:40 ` rguenth at gcc dot gnu dot org 2010-04-08 9:02 ` manu at gcc dot gnu dot org 2010-04-08 10:48 ` ebotcazou at gcc dot gnu dot org 2010-04-08 12:53 ` bangerth at gmail dot com 2010-04-08 15:57 ` jason at gcc dot gnu dot org 2010-04-08 22:30 ` pinskia at gcc dot gnu dot org 2010-04-09 4:44 ` jason at gcc dot gnu dot org 2010-04-20 20:44 ` [Bug c++/43680] [DR 1022] " mmitchel at gcc dot gnu dot org 2010-04-20 22:03 ` jason at gcc dot gnu dot org 2010-04-20 22:19 ` mark at codesourcery dot com 2010-04-20 23:11 ` jason at gcc dot gnu dot org 2010-05-03 21:17 ` jason at gcc dot gnu dot org 2010-05-04 4:44 ` 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=20100407215601.27108.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).