public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/48679] [4.7 regression] bootstrap comparison failures on m68k-linux Date: Sat, 28 May 2011 10:53:00 -0000 [thread overview] Message-ID: <bug-48679-4-be6GwcJFbI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48679-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48679 Mikael Pettersson <mikpe at it dot uu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #8 from Mikael Pettersson <mikpe at it dot uu.se> 2011-05-28 10:52:21 UTC --- The bootstrap comparison failures were fixed by r173393: Author: bernds Date: Wed May 4 20:24:15 2011 New Revision: 173393 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173393 Log: PR rtl-optimization/47612 * df-problems.c (can_move_insns_across): Don't pick a cc0 setter as the last insn of the sequence to be moved. which is a little unexpected since the bug it fixed (PR47612) didn't affect m68k-linux prior to the large IRA update.
prev parent reply other threads:[~2011-05-28 10:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-19 7:42 [Bug bootstrap/48679] New: " mikpe at it dot uu.se 2011-04-19 9:24 ` [Bug bootstrap/48679] " schwab@linux-m68k.org 2011-04-19 9:51 ` rguenth at gcc dot gnu.org 2011-04-19 9:59 ` mikpe at it dot uu.se 2011-05-04 21:29 ` mikpe at it dot uu.se 2011-05-06 11:35 ` mikpe at it dot uu.se 2011-05-07 16:53 ` mikpe at it dot uu.se 2011-05-12 23:02 ` mikpe at it dot uu.se 2011-05-16 12:44 ` mikpe at it dot uu.se 2011-05-28 10:53 ` mikpe at it dot uu.se [this message]
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-48679-4-be6GwcJFbI@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).