public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64159] [5.0 regression] FAIL: gcc.dg/tree-ssa/ssa-dom-cse-2.c scan-tree-dump optimized "return 28;" Date: Wed, 03 Dec 2014 00:08:00 -0000 [thread overview] Message-ID: <bug-64159-4-tZCGPoZ9hF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64159-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64159 Andreas Schwab <schwab@linux-m68k.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |5.0
next prev parent reply other threads:[~2014-12-03 0:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-03 0:08 [Bug tree-optimization/64159] New: " schwab@linux-m68k.org 2014-12-03 0:08 ` schwab@linux-m68k.org [this message] 2014-12-03 2:05 ` [Bug tree-optimization/64159] " pinskia at gcc dot gnu.org 2014-12-03 10:10 ` [Bug target/64159] [5 Regression] " rguenth at gcc dot gnu.org 2015-01-22 13:10 ` ro at gcc dot gnu.org 2015-01-29 19:17 ` dje at gcc dot gnu.org 2015-01-31 14:58 ` dje at gcc dot gnu.org 2015-02-01 21:14 ` dje at gcc dot gnu.org 2015-02-01 22:28 ` pinskia at gcc dot gnu.org 2015-05-27 15:48 ` ktkachov 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-64159-4-tZCGPoZ9hF@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).