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 rtl-optimization/64158] New: [5.0 regression] FAIL: gcc.dg/pr44194-1.c scan-rtl-dump dse1 "global deletions = (2|3)" Date: Tue, 02 Dec 2014 23:45:00 -0000 [thread overview] Message-ID: <bug-64158-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64158 Bug ID: 64158 Summary: [5.0 regression] FAIL: gcc.dg/pr44194-1.c scan-rtl-dump dse1 "global deletions = (2|3)" Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: schwab@linux-m68k.org Target: powerpc64-*-* $ grep "global deletions =" pr44194-1.c.209r.dse1 dse: local deletions = 0, global deletions = 0, spill deletions = 0
next reply other threads:[~2014-12-02 23:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-02 23:45 schwab@linux-m68k.org [this message] 2014-12-02 23:45 ` [Bug rtl-optimization/64158] " schwab@linux-m68k.org 2015-02-20 11:27 ` [Bug rtl-optimization/64158] [5 Regression] " jakub at gcc dot gnu.org 2015-02-20 11:59 ` [Bug testsuite/64158] " jakub at gcc dot gnu.org 2015-02-20 13:04 ` schwab@linux-m68k.org 2015-02-20 16:45 ` jakub at gcc dot gnu.org 2015-02-23 21:00 ` jakub 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-64158-4@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).