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++/106858] [12/13 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'baselink' in cp_ubsan_maybe_instrument_member_access, at cp/cp-ubsan.cc:172 since r12-5835-g0ab29cf0bb68960c Date: Fri, 16 Sep 2022 12:44:07 +0000 [thread overview] Message-ID: <bug-106858-4-udsFLA2Xn6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106858 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:39dc66558e066e67fd40f21f53cee80989ae742d commit r13-2696-g39dc66558e066e67fd40f21f53cee80989ae742d Author: Jason Merrill <jason@redhat.com> Date: Thu Sep 15 22:55:50 2022 +0200 c++: member fn in omp loc list [PR106858] this-f names a member function, which isn't an addressable lvalue. Give a helpful error instead of crashing. The first hunk makes the error range cover the whole expression. PR c++/106858 gcc/cp/ChangeLog: * parser.cc (cp_parser_omp_var_list_no_open): Pass the initial token location down. * semantics.cc (finish_omp_clauses): Check invalid_nonstatic_memfn_p. * typeck.cc (invalid_nonstatic_memfn_p): Handle null TREE_TYPE. gcc/testsuite/ChangeLog: * g++.dg/gomp/map-3.C: New test.
next prev parent reply other threads:[~2022-09-16 12:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:14 [Bug c++/106858] New: [12/13 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'baselink' in cp_ubsan_maybe_instrument_member_access, at cp/cp-ubsan.cc:172 gscfq@t-online.de 2022-09-07 8:26 ` [Bug c++/106858] " rguenth at gcc dot gnu.org 2022-09-07 12:05 ` [Bug c++/106858] [12/13 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'baselink' in cp_ubsan_maybe_instrument_member_access, at cp/cp-ubsan.cc:172 since r12-5835-g0ab29cf0bb68960c marxin at gcc dot gnu.org 2022-09-16 12:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-19 6:07 ` [Bug c++/106858] [12 " rguenth at gcc dot gnu.org 2022-10-19 6:08 ` rguenth at gcc dot gnu.org 2023-05-08 12:25 ` rguenth at gcc dot gnu.org 2024-06-20 9:10 ` rguenth 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-106858-4-udsFLA2Xn6@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).