public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66549] [5/6 Regression] ICE on valid in OMP parallel region Date: Fri, 19 Jun 2015 12:50:00 -0000 [thread overview] Message-ID: <bug-66549-4-EV7UZ5cKyQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66549 --- Comment #5 from Mikael Morin <mikael at gcc dot gnu.org> --- Author: mikael Date: Fri Jun 19 12:50:00 2015 New Revision: 224648 URL: https://gcc.gnu.org/viewcvs?rev=224648&root=gcc&view=rev Log: Fix openmp global state fortran regression PR fortran/66549 gcc/fortran/ * resolve.c (resolve_global_procedure): Don't save and restore OpenMP state around the call to gfc_resolve. (gfc_resolve): Save OpenMP state on entry and restore it on return. gcc/testsuite/ * gfortran.dg/gomp/omp_parallel_1.f90: New file. Added: trunk/gcc/testsuite/gfortran.dg/gomp/omp_parallel_1.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-06-19 12:50 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-16 2:15 [Bug fortran/66549] New: " abensonca at gmail dot com 2015-06-16 16:10 ` [Bug fortran/66549] [Regression] " kargl at gcc dot gnu.org 2015-06-17 10:54 ` [Bug fortran/66549] [5/6 Regression] " dominiq at lps dot ens.fr 2015-06-17 10:57 ` jakub at gcc dot gnu.org 2015-06-17 19:36 ` mikael at gcc dot gnu.org 2015-06-17 21:08 ` mikael at gcc dot gnu.org 2015-06-19 12:50 ` mikael at gcc dot gnu.org [this message] 2015-06-19 16:35 ` mikael at gcc dot gnu.org 2015-06-22 12:02 ` [Bug fortran/66549] [5 " rguenth at gcc dot gnu.org 2015-06-24 9:16 ` mikael at gcc dot gnu.org 2015-06-24 9:22 ` [Bug fortran/66549] [5/6 " mikael 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-66549-4-EV7UZ5cKyQ@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).