public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/59985] stage2/3 compare error on lto-streamer-in.o Date: Thu, 30 Jan 2014 17:02:00 -0000 [thread overview] Message-ID: <bug-59985-4-XQXYRMPn0Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59985-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59985 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It seems the reason for the different chosen alternative for the last anddi3_insn is reload_sum. overall, losers and reload_nregs are the same for nalt 4 and 5, 4 is currently best alternative in both cases, but reload_sum is in one case 0 and in one case 1. bb_reload_num is 13 in one case and 14 in the other case, while last_reload is 14 in both cases.
next prev parent reply other threads:[~2014-01-30 17:02 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-29 14:57 [Bug bootstrap/59985] New: " bernd.edlinger at hotmail dot de 2014-01-29 15:31 ` [Bug bootstrap/59985] " rguenth at gcc dot gnu.org 2014-01-30 7:40 ` bernd.edlinger at hotmail dot de 2014-01-30 7:58 ` jakub at gcc dot gnu.org 2014-01-30 8:19 ` bernd.edlinger at hotmail dot de 2014-01-30 8:22 ` jakub at gcc dot gnu.org 2014-01-30 8:54 ` bernd.edlinger at hotmail dot de 2014-01-30 12:20 ` jakub at gcc dot gnu.org 2014-01-30 13:40 ` jakub at gcc dot gnu.org 2014-01-30 15:55 ` jakub at gcc dot gnu.org 2014-01-30 17:02 ` jakub at gcc dot gnu.org [this message] 2014-01-30 17:19 ` jakub at gcc dot gnu.org 2014-01-30 17:50 ` vmakarov at gcc dot gnu.org 2014-01-31 13:12 ` bernd.edlinger at hotmail dot de 2014-01-31 23:57 ` vmakarov at gcc dot gnu.org 2014-02-01 8:44 ` 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-59985-4-XQXYRMPn0Y@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).