public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38650] [4.3/4.4 regression] Trouble with volatile and #pragma omp for
Date: Sun, 28 Dec 2008 20:08:00 -0000	[thread overview]
Message-ID: <20081228200724.4042.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38650-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jakub at gcc dot gnu dot org  2008-12-28 20:07 -------
Subject: Bug 38650

Author: jakub
Date: Sun Dec 28 20:06:00 2008
New Revision: 142940

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142940
Log:
        PR c++/38650
        * semantics.c (finish_omp_for): Don't add CLEANUP_POINT_EXPR
        around volatile iteration var in condition and/or increment
        expression.

        * testsuite/libgomp.c/pr38650.c: New test.
        * testsuite/libgomp.c++/pr38650.C: New test.

Added:
    trunk/libgomp/testsuite/libgomp.c++/pr38650.C
    trunk/libgomp/testsuite/libgomp.c/pr38650.c
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/semantics.c
    trunk/libgomp/ChangeLog


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38650


  parent reply	other threads:[~2008-12-28 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-28  0:23 [Bug c++/38650] New: " reichelt at gcc dot gnu dot org
2008-12-28  0:24 ` [Bug c++/38650] " reichelt at gcc dot gnu dot org
2008-12-28 17:52 ` jakub at gcc dot gnu dot org
2008-12-28 20:08 ` jakub at gcc dot gnu dot org [this message]
2008-12-28 20:12 ` [Bug c++/38650] [4.3 " jakub at gcc dot gnu dot org
2008-12-29 23:01 ` rguenth at gcc dot gnu dot org
2009-01-24 10:28 ` rguenth at gcc dot gnu dot org
2009-08-04 12:46 ` rguenth at gcc dot gnu dot org
2010-05-22 18:28 ` rguenth 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=20081228200724.4042.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).