public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46315] [4.5 Regression] gcc-4.5.1 -O2 -fno-strict-overflow causes bad code generation Date: Fri, 05 Nov 2010 16:43:00 -0000 [thread overview] Message-ID: <bug-46315-4-D8WdvGwNkf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46315-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46315 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2010.11.05 16:43:32 Known to work| |4.4.4, 4.6.0 Target Milestone|--- |4.5.2 Summary|gcc-4.5.1 -O2 |[4.5 Regression] gcc-4.5.1 |-fno-strict-overflow causes |-O2 -fno-strict-overflow |bad code generation |causes bad code generation Ever Confirmed|0 |1 Known to fail| |4.5.0, 4.5.1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-05 16:43:32 UTC --- Confirmed.
next prev parent reply other threads:[~2010-11-05 16:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-05 16:27 [Bug c/46315] New: " zorry at gentoo dot org 2010-11-05 16:43 ` rguenth at gcc dot gnu.org [this message] 2010-11-05 16:47 ` [Bug tree-optimization/46315] [4.5 Regression] " rguenth at gcc dot gnu.org 2010-11-09 4:50 ` dirtyepic at gentoo dot org 2010-11-12 15:47 ` rguenth at gcc dot gnu.org 2010-11-13 19:48 ` [Bug rtl-optimization/46315] " rguenth at gcc dot gnu.org 2010-11-13 22:29 ` ebotcazou at gcc dot gnu.org 2010-11-14 11:38 ` ebotcazou at gcc dot gnu.org 2010-11-16 0:42 ` [Bug rtl-optimization/46315] [4.5 regression] -O2 -fno-strict-overflow causes wrong " ebotcazou at gcc dot gnu.org 2010-11-16 22:15 ` ebotcazou at gcc dot gnu.org 2010-11-16 22:18 ` ebotcazou at gcc dot gnu.org 2010-11-16 22:22 ` ebotcazou 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-46315-4-D8WdvGwNkf@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).