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/49911] SRA + DOM + -fstrict-enums incorrectly remove predicate Date: Mon, 01 Aug 2011 08:34:00 -0000 [thread overview] Message-ID: <bug-49911-4-gQyz7rc4j6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49911-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49911 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamborm at gcc dot gnu.org Summary|vrp2 + -fstrict-enums |SRA + DOM + -fstrict-enums |incorrectly remove |incorrectly remove |predicate |predicate --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-08-01 08:34:04 UTC --- I'm looking into the DOM problem - martin, can you look at the SRA bug?
next prev parent reply other threads:[~2011-08-01 8:34 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-30 14:35 [Bug tree-optimization/49911] New: vrp2 " rafael.espindola at gmail dot com 2011-07-31 9:57 ` [Bug tree-optimization/49911] " rguenth at gcc dot gnu.org 2011-07-31 13:39 ` rafael.espindola at gmail dot com 2011-07-31 13:57 ` rafael.espindola at gmail dot com 2011-08-01 8:33 ` rguenth at gcc dot gnu.org 2011-08-01 8:34 ` rguenth at gcc dot gnu.org [this message] 2011-08-01 8:42 ` [Bug tree-optimization/49911] SRA + DOM " rguenth at gcc dot gnu.org 2011-08-01 8:45 ` [Bug tree-optimization/49911] SRA + DOM + VRP " rguenth at gcc dot gnu.org 2011-08-01 8:49 ` rguenth at gcc dot gnu.org 2011-08-01 9:06 ` rguenth at gcc dot gnu.org 2011-08-04 19:00 ` rafael.espindola at gmail dot com 2011-08-06 15:59 ` ebotcazou at gcc dot gnu.org 2011-08-06 16:08 ` ebotcazou at gcc dot gnu.org 2011-08-11 12:34 ` jamborm at gcc dot gnu.org 2011-08-11 13:37 ` rguenth at gcc dot gnu.org 2011-08-11 13:42 ` rguenth at gcc dot gnu.org 2011-08-12 8:02 ` ebotcazou at gcc dot gnu.org 2011-08-17 22:21 ` rafael.espindola at gmail dot com 2011-09-05 16:36 ` jamborm at gcc dot gnu.org 2011-09-05 17:15 ` rafael.espindola at gmail dot com 2011-09-06 7:30 ` rguenth at gcc dot gnu.org 2011-09-07 14:31 ` jamborm at gcc dot gnu.org 2011-09-07 15:04 ` rafael.espindola at gmail dot com 2011-09-07 15:49 ` jamborm at gcc dot gnu.org 2011-09-08 14:01 ` jamborm at gcc dot gnu.org 2011-09-08 17:30 ` jamborm at gcc dot gnu.org 2011-09-09 9:37 ` jamborm 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-49911-4-gQyz7rc4j6@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).