public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/52348] OpenMP incorrectly parallelizes loops (wrong iteration count) Date: Thu, 23 Feb 2012 10:08:00 -0000 [thread overview] Message-ID: <bug-52348-4-WqDgMDZiiZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52348-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52348 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-02-23 Summary|[4.5/4.6/4.7] OpenMP |OpenMP incorrectly |incorrectly parallelizes |parallelizes loops (wrong |loops (wrong iteration |iteration count) |count) | Ever Confirmed|0 |1 Known to fail| |4.3.6, 4.4.6, 4.5.3, 4.6.2, | |4.7.0 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-23 09:58:24 UTC --- With 4.3.x we warned testcase.c: In function 'main': testcase.c:26: warning: iteration variable 'x' is unsigned and up to 4.6.2 we produce INT32_MAX: 0 / 65535 UINT32_MAX: 32768 / 65535 but on trunk (4.7) we say INT32_MAX: 0 / 65535 UINT32_MAX: 65535 / 65535 Confirmed that ICC produces INT32_MAX: 65535 / 65535 UINT32_MAX: 65535 / 65535
next prev parent reply other threads:[~2012-02-23 9:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-23 9:22 [Bug libgomp/52348] New: [4.5/4.6] " ua_gcc_bugzilla@binary-island.eu 2012-02-23 9:53 ` [Bug libgomp/52348] [4.5/4.6/4.7] " ua_gcc_bugzilla@binary-island.eu 2012-02-23 10:08 ` rguenth at gcc dot gnu.org [this message] 2012-02-23 10:29 ` [Bug libgomp/52348] " ua_gcc_bugzilla@binary-island.eu 2012-02-23 10:39 ` [Bug libgomp/52348] [4.5/4.6/4.7] " jakub at gcc dot gnu.org 2012-02-23 10:47 ` ua_gcc_bugzilla@binary-island.eu
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-52348-4-WqDgMDZiiZ@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).