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 rtl-optimization/65123] [5 regression] lra remat places insn which breaks data flow Date: Fri, 20 Feb 2015 07:46:00 -0000 [thread overview] Message-ID: <bug-65123-4-hpWuh8cBda@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65123-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65123 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ra, wrong-code Priority|P3 |P1 Target Milestone|--- |5.0 Summary|[5.0 regression] lra remat |[5 regression] lra remat |places insn which breaks |places insn which breaks |data flow |data flow
next prev parent reply other threads:[~2015-02-20 7:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-19 16:51 [Bug rtl-optimization/65123] New: " krebbel at gcc dot gnu.org 2015-02-20 7:46 ` rguenth at gcc dot gnu.org [this message] 2015-02-20 22:54 ` [Bug rtl-optimization/65123] [5 regression] " vmakarov at gcc dot gnu.org 2015-02-24 19:22 ` vmakarov at gcc dot gnu.org 2015-02-24 19:32 ` 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-65123-4-hpWuh8cBda@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).