public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42640] wrong code for -ftree-loop-distribution in 175.vpr
Date: Mon, 08 Feb 2010 15:28:00 -0000 [thread overview]
Message-ID: <20100208152821.26633.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42640-4503@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from zsojka at seznam dot cz 2010-02-08 15:28 -------
I can reproduce this on x86_64, trunk r156598 and 4.4 r156256.
Also, bootstrap fails for me with BOOT_CFLAGS="-O2 -ftree-loop-distribution":
Comparing stages 2 and 3
warning: gcc/cc1plus-checksum.o differs
warning: gcc/cc1-checksum.o differs
Bootstrap comparison failure!
libiberty/sha1.o differs
make[2]: *** [compare] Error 1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42640
next prev parent reply other threads:[~2010-02-08 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:10 [Bug tree-optimization/42640] New: " janis at gcc dot gnu dot org
2010-01-06 23:12 ` [Bug tree-optimization/42640] " janis at gcc dot gnu dot org
2010-02-08 15:28 ` zsojka at seznam dot cz [this message]
2010-02-23 19:27 ` janis at gcc dot gnu dot org
2010-02-23 20:38 ` bangerth at gmail dot com
2010-02-23 21:07 ` spop at gcc dot gnu dot org
2010-03-02 10:23 ` spop at gcc dot gnu dot org
2010-03-02 10:25 ` spop at gcc dot gnu dot 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=20100208152821.26633.qmail@sourceware.org \
--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: link
Be 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).