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/53580] Internal Segmentation fault in nested "omp parallel", "omp parallel for" and "omp parallel for reduction" Directives
Date: Thu, 14 Jun 2012 17:49:00 -0000	[thread overview]
Message-ID: <bug-53580-4-5mJ7zEkHSS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53580-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-06-14 17:48:42 UTC ---
Author: jakub
Date: Thu Jun 14 17:48:38 2012
New Revision: 188625

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188625
Log:
    Backported from mainline
    2012-06-07  Jakub Jelinek  <jakub@redhat.com>

    PR middle-end/53580
    * omp-low.c (scan_omp_1_stmt): If check_omp_nesting_restrictions
    returns false, replace stmt with GIMPLE_NOP.
    (check_omp_nesting_restrictions): Instead of issuing warnings,
    issue errors and return false if any errors were reported.

    * gcc.dg/gomp/nesting-1.c: Expect errors rather than warnings.
    * gcc.dg/gomp/critical-4.c: Likewise.
    * gfortran.dg/gomp/appendix-a/a.35.1.f90: Likewise.
    * gfortran.dg/gomp/appendix-a/a.35.3.f90: Likewise.
    * gfortran.dg/gomp/appendix-a/a.35.4.f90: Likewise.
    * gfortran.dg/gomp/appendix-a/a.35.6.f90: Likewise.
    * c-c++-common/gomp/pr53580.c: New test.

    * testsuite/libgomp.c/pr26943-2.c: Remove #pragma omp barrier,
    use GOMP_barrier () call instead.
    * testsuite/libgomp.c/pr26943-3.c: Likewise.
    * testsuite/libgomp.c/pr26943-4.c: Likewise.
    * testsuite/libgomp.fortran/vla4.f90: Remove !$omp barrier,
    call GOMP_barrier instead.
    * testsuite/libgomp.fortran/vla5.f90: Likewise.

Added:
    branches/gcc-4_7-branch/gcc/testsuite/c-c++-common/gomp/pr53580.c
Modified:
    branches/gcc-4_7-branch/gcc/ChangeLog
    branches/gcc-4_7-branch/gcc/omp-low.c
    branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/gomp/critical-4.c
    branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/gomp/nesting-1.c
   
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.35.1.f90
   
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.35.3.f90
   
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.35.4.f90
   
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.35.6.f90
    branches/gcc-4_7-branch/libgomp/ChangeLog
    branches/gcc-4_7-branch/libgomp/testsuite/libgomp.c/pr26943-2.c
    branches/gcc-4_7-branch/libgomp/testsuite/libgomp.c/pr26943-3.c
    branches/gcc-4_7-branch/libgomp/testsuite/libgomp.c/pr26943-4.c
    branches/gcc-4_7-branch/libgomp/testsuite/libgomp.fortran/vla4.f90
    branches/gcc-4_7-branch/libgomp/testsuite/libgomp.fortran/vla5.f90


  parent reply	other threads:[~2012-06-14 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  4:30 [Bug c/53580] New: " fedediazceo at gmail dot com
2012-06-05  6:34 ` [Bug c/53580] " jakub at gcc dot gnu.org
2012-06-05 11:07 ` fernando at info dot unlp.edu.ar
2012-06-06 16:06 ` jakub at gcc dot gnu.org
2012-06-06 17:42 ` jakub at gcc dot gnu.org
2012-06-06 17:51 ` jakub at gcc dot gnu.org
2012-06-07  6:37 ` jakub at gcc dot gnu.org
2012-06-14 17:49 ` jakub at gcc dot gnu.org [this message]
2012-06-15 11:12 ` jakub 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-53580-4-5mJ7zEkHSS@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: 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).