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++/98072] [9/10/11 Regression] ICE in cp_parser_omp_var_list_no_open, at cp/parser.c:34843
Date: Tue, 01 Dec 2020 20:46:10 +0000	[thread overview]
Message-ID: <bug-98072-4-58cnixtZ5y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98072-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98072

--- Comment #4 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:91ddf867a57b028ab322b737ea8355d5a472cd44

commit r11-5623-g91ddf867a57b028ab322b737ea8355d5a472cd44
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Dec 1 21:41:44 2020 +0100

    openmp: Avoid ICE on depend clause on depobj OpenMP construct [PR98072]

    Since r11-5430 we ICE on the following testcase.  When parsing the depobj
    directive we don't really use cp_parser_omp_all_clauses routine which ATM
    disables generation of location wrappers and the newly added assertion
    that there are no location wrappers thus triggers.

    Fixed by adding the location wrappers suppression sentinel.

    Longer term, we should handle location wrappers inside of OpenMP clauses.

    2020-12-01  Jakub Jelinek  <jakub@redhat.com>

            PR c++/98072
            * parser.c (cp_parser_omp_depobj): Suppress location wrappers when
            parsing depend clause.

            * c-c++-common/gomp/depobj-2.c: New test.

  parent reply	other threads:[~2020-12-01 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01  2:43 [Bug c++/98072] New: [11 " asolokha at gmx dot com
2020-12-01  8:22 ` [Bug c++/98072] " rguenth at gcc dot gnu.org
2020-12-01  9:33 ` [Bug c++/98072] [9/10/11 " jakub at gcc dot gnu.org
2020-12-01  9:42 ` jakub at gcc dot gnu.org
2020-12-01 10:33 ` tschwinge at gcc dot gnu.org
2020-12-01 20:46 ` cvs-commit at gcc dot gnu.org [this message]
2020-12-02 18:11 ` [Bug c++/98072] [9/10 " jakub at gcc dot gnu.org
2021-01-06  9:39 ` cvs-commit at gcc dot gnu.org
2021-01-06  9:43 ` [Bug c++/98072] [9 " jakub at gcc dot gnu.org
2021-04-20 23:30 ` cvs-commit at gcc dot gnu.org
2021-04-22 13:27 ` 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-98072-4-58cnixtZ5y@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).