public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94512] [9/10 Regression] ICE in tsubst_expr, at cp/pt.c:18210
Date: Tue, 07 Apr 2020 12:32:17 +0000 [thread overview]
Message-ID: <bug-94512-4-8FICWnsFrC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94512-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94512
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:4df50a059fbd4d4a1cb067bd43caccdfca0327a8
commit r10-7585-g4df50a059fbd4d4a1cb067bd43caccdfca0327a8
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Apr 7 14:30:53 2020 +0200
openmp: Fix parallel master error recovery [PR94512]
We need to set OMP_PARALLEL_COMBINED only if the parsing of omp_master
succeeded, because otherwise there is no nested master construct in the
parallel.
2020-04-07 Jakub Jelinek <jakub@redhat.com>
PR c++/94512
* c-parser.c (c_parser_omp_parallel): Set OMP_PARALLEL_COMBINED
if c_parser_omp_master succeeded.
* parser.c (cp_parser_omp_parallel): Set OMP_PARALLEL_COMBINED
if cp_parser_omp_master succeeded.
* g++.dg/gomp/pr94512.C: New test.
next prev parent reply other threads:[~2020-04-07 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 9:23 [Bug c++/94512] New: [10 " asolokha at gmx dot com
2020-04-07 9:42 ` [Bug c++/94512] " rguenth at gcc dot gnu.org
2020-04-07 10:18 ` [Bug c++/94512] [9/10 " jakub at gcc dot gnu.org
2020-04-07 10:44 ` jakub at gcc dot gnu.org
2020-04-07 12:32 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-07 19:05 ` cvs-commit at gcc dot gnu.org
2020-04-07 20:02 ` 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-94512-4-8FICWnsFrC@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).