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/104532] ICE in lvalue_p, at c/c-typeck.cc:4987 Date: Thu, 17 Feb 2022 09:31:07 +0000 [thread overview] Message-ID: <bug-104532-4-MfQlfts4R4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104532-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104532 --- 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:f99ad11af953568e1a01e4f4fe31cba0f11879a5 commit r12-7274-gf99ad11af953568e1a01e4f4fe31cba0f11879a5 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Feb 17 10:29:06 2022 +0100 openmp: Ensure proper diagnostics for -> in map/to/from clauses [PR104532] The following patch uses the functions normal CPP_DEREF parsing uses, i.e. convert_lvalue_to_rvalue and build_indirect_ref, instead of blindly calling build_simple_mem_ref, so that if the variable does not have correct type, we properly diagnose it instead of ICEing on it. 2022-02-17 Jakub Jelinek <jakub@redhat.com> PR c/104532 * c-parser.cc (c_parser_omp_variable_list): For CPP_DEREF, use convert_lvalue_to_rvalue and build_indirect_ref instead of build_simple_mem_ref. * gcc.dg/gomp/pr104532.c: New test.
next prev parent reply other threads:[~2022-02-17 9:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-14 19:53 [Bug c/104532] New: " gscfq@t-online.de 2022-02-15 17:01 ` [Bug c/104532] " jakub at gcc dot gnu.org 2022-02-16 13:34 ` jakub at gcc dot gnu.org 2022-02-17 9:31 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-17 9:35 ` 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-104532-4-MfQlfts4R4@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).