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 c/61050] OpenMP: wrong behavior of 'omp for' on corner cases Date: Sun, 04 May 2014 05:53:00 -0000 [thread overview] Message-ID: <bug-61050-4-dXL8bgLPNU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61050-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61050 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |jakub at gcc dot gnu.org Resolution|--- |INVALID --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This is undefined behavior. See OpenMP 4.0, 2.6, lines 18-26 on page 52: "The following restrictions also apply: - If test-expr is of the form var relational-op b and relational-op is < or <= then incr-expr must cause var to increase on each iteration of the loop. If test-expr is of the form var relational-op b and relational-op is > or >= then incr-expr must cause var to decrease on each iteration of the loop. - If test-expr is of the form b relational-op var and relational-op is < or <= then incr-expr must cause var to decrease on each iteration of the loop. If test-expr is of the form b relational-op var and relational-op is > or >= then incr-expr must cause var to increase on each iteration of the loop." Other versions of the standard have similar wording. Not every valid C/C++ for loop is valid OpenMP #pragma omp {for,simd,distribute} loop.
next prev parent reply other threads:[~2014-05-04 5:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-03 22:04 [Bug c/61050] New: " guido at vanguardiasur dot com.ar 2014-05-04 5:53 ` jakub at gcc dot gnu.org [this message] 2014-05-04 21:52 ` [Bug c/61050] " guido at vanguardiasur dot com.ar
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-61050-4-dXL8bgLPNU@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).