public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59379] gomp_init_num_threads is compiled into an infinite loop with --with-arch=corei7 --with-cpu=slm Date: Wed, 04 Dec 2013 00:48:00 -0000 [thread overview] Message-ID: <bug-59379-4-Hf0lVvCgx5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59379-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59379 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-12-04 Ever confirmed|0 |1 --- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> --- The difference starts in ivopts pass: diff -upr good/test.c.120t.ivopts bad/test.c.120t.ivopts --- good/test.c.120t.ivopts 2013-12-03 16:46:21.995210047 -0800 +++ bad/test.c.120t.ivopts 2013-12-03 16:46:34.847986232 -0800 @@ -13,6 +13,7 @@ gomp_init_num_threads () long unsigned int _13; long unsigned int gomp_cpuset_size.2_14; void * gomp_cpusetp.3_17; + long unsigned int _19; long unsigned int gomp_cpuset_size.1_20; int _22; long unsigned int gomp_cpuset_size.1_25; @@ -39,6 +40,7 @@ gomp_init_num_threads () struct cpu_set_t * prephitmp_89; struct cpu_set_t * prephitmp_90; long unsigned int pretmp_91; + long unsigned int _92; long unsigned int pretmp_93; long unsigned int pretmp_95; long unsigned int prephitmp_96; @@ -93,7 +95,9 @@ gomp_init_num_threads () <bb 8>: # i_76 = PHI <i_48(12), i_47(7)> i_48 = i_76 + 18446744073709551615; - if (i_47 > i_48) + _92 = i_47 * 18446744069414584320; + i_94 = i_48 + _92; + if (i_47 > i_94) goto <bb 9>; else goto <bb 11>; @@ -118,7 +122,9 @@ gomp_init_num_threads () goto <bb 13>; <bb 11>: - if (i_48 != 0) + _19 = i_47 * 18446744069414584320; + i_69 = _19 + i_48; + if (i_69 != 0) goto <bb 12>; else goto <bb 13>;
next prev parent reply other threads:[~2013-12-04 0:48 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-03 21:40 [Bug target/59379] New: " hjl.tools at gmail dot com 2013-12-03 21:46 ` [Bug target/59379] " octoploid at yandex dot com 2013-12-03 21:51 ` hjl.tools at gmail dot com 2013-12-03 21:52 ` hjl.tools at gmail dot com 2013-12-04 0:41 ` hjl.tools at gmail dot com 2013-12-04 0:48 ` hjl.tools at gmail dot com [this message] 2013-12-04 10:52 ` [Bug target/59379] [4.9 Regression] " hjl.tools at gmail dot com 2013-12-04 23:39 ` hjl.tools at gmail dot com 2013-12-05 3:11 ` hjl.tools at gmail dot com 2013-12-05 11:17 ` rguenth at gcc dot gnu.org 2013-12-06 1:45 ` hjl.tools at gmail dot com 2013-12-19 15:37 ` rguenth at gcc dot gnu.org 2013-12-26 12:41 ` izamyatin at gmail dot com 2013-12-26 12:57 ` hjl.tools at gmail dot com 2013-12-26 14:41 ` hjl.tools at gmail dot com 2013-12-30 21:16 ` izamyatin at gmail dot com 2013-12-31 7:02 ` izamyatin at gmail dot com 2014-01-18 17:13 ` hjl.tools at gmail dot com 2014-01-18 19:47 ` ubizjak at gmail dot com 2014-01-19 9:51 ` ubizjak at gmail dot com 2014-01-19 14:18 ` hjl.tools at gmail dot com 2014-01-19 15:48 ` uros at gcc dot gnu.org 2014-01-22 18:29 ` uros at gcc dot gnu.org 2014-01-22 18:40 ` ubizjak at gmail dot com
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-59379-4-Hf0lVvCgx5@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).