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 testsuite/64039] [5 Regression] FAIL: gcc.dg/tree-ssa/ssa-dom-cse-2.c scan-tree-dump optimized "return 28;" Date: Mon, 24 Nov 2014 11:04:00 -0000 [thread overview] Message-ID: <bug-64039-4-Ke9Zr2X5x3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64039-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64039 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2014-11-24 Component|tree-optimization |testsuite Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Target Milestone|--- |5.0 Summary|FAIL: |[5 Regression] FAIL: |gcc.dg/tree-ssa/ssa-dom-cse |gcc.dg/tree-ssa/ssa-dom-cse |-2.c scan-tree-dump |-2.c scan-tree-dump |optimized "return 28;" |optimized "return 28;" Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- a = *L$C0000; ok, so PA has a similar issue as aarch64 (PR63679), I suppose for those targets we need to XFAIL the test (it's a known missed-optimization tracked in that PR). I'll take care of this.
next prev parent reply other threads:[~2014-11-24 11:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-24 1:01 [Bug tree-optimization/64039] New: " danglin at gcc dot gnu.org 2014-11-24 11:04 ` rguenth at gcc dot gnu.org [this message] 2014-11-24 11:07 ` [Bug testsuite/64039] [5 Regression] " rguenth at gcc dot gnu.org 2014-11-24 11:07 ` rguenth 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-64039-4-Ke9Zr2X5x3@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).