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/46194] New: [4.5/4.6 Regression] gcc.dg/graphite/block-0.c FAILs with -ftree-parallelize-loops Date: Wed, 27 Oct 2010 00:27:00 -0000 [thread overview] Message-ID: <bug-46194-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46194 Summary: [4.5/4.6 Regression] gcc.dg/graphite/block-0.c FAILs with -ftree-parallelize-loops Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Graphite is not needed to reproduce this. The output value looks "random", it differs in different runs. Output (with #define DEBUG 1): $ gcc -O -ftree-parallelize-loops=2 block-0.c && ./a.out res = 2155 Aborted $ ./a.out res = 2156 Aborted $ ./a.out res = 2201 Aborted Tested revisions: r165915 - fail r153685 - fail 4.5 r165781 - fail 4.4 r165754 - OK
next reply other threads:[~2010-10-27 0:27 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-27 0:27 zsojka at seznam dot cz [this message] 2010-10-27 10:19 ` [Bug tree-optimization/46194] " hjl.tools at gmail dot com 2010-10-27 20:50 ` rguenth at gcc dot gnu.org 2010-11-12 15:19 ` rguenth at gcc dot gnu.org 2010-12-16 13:28 ` rguenth at gcc dot gnu.org 2010-12-31 12:02 ` jakub at gcc dot gnu.org 2011-02-03 18:11 ` Sebastian Pop 2010-12-31 13:09 ` zsojka at seznam dot cz 2011-02-03 8:42 ` jakub at gcc dot gnu.org 2011-02-03 17:34 ` spop at gcc dot gnu.org 2011-02-03 18:11 ` sebpop at gmail dot com 2011-02-03 19:54 ` Sebastian Pop 2011-02-03 18:21 ` spop at gcc dot gnu.org 2011-02-03 19:55 ` sebpop at gmail dot com 2011-02-04 4:00 ` spop at gcc dot gnu.org 2011-02-05 1:39 ` spop at gcc dot gnu.org 2011-02-05 1:42 ` spop at gcc dot gnu.org 2011-02-07 22:58 ` [Bug tree-optimization/46194] [4.5 " spop at gcc dot gnu.org 2011-04-18 14:44 ` rguenth at gcc dot gnu.org 2011-04-18 16:11 ` spop at gcc dot gnu.org 2011-04-19 16:26 ` spop at gcc dot gnu.org 2011-04-28 16:02 ` rguenth at gcc dot gnu.org 2011-07-26 19:39 ` spop at gcc dot gnu.org 2011-07-27 18:26 ` spop 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-46194-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).