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++/99283] [modules] ICE in assert_definition, at cp/module.cc:4608 Date: Tue, 30 Mar 2021 16:52:26 +0000 [thread overview] Message-ID: <bug-99283-4-Ap0oImktnL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99283-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99283 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>: https://gcc.gnu.org/g:5f3c6027257118469a722816e228394b5978ddb0 commit r11-7915-g5f3c6027257118469a722816e228394b5978ddb0 Author: Nathan Sidwell <nathan@acm.org> Date: Tue Mar 30 09:45:59 2021 -0700 c++: duplicate const static members [PR 99283] This is the bug that keeps on giving. Reducing it has been successful at hitting other defects. In this case, some more specialization hash table fun, plus an issue with reading in a definition of a duplicated declaration. At least I discovered a null context check is no longer needed. PR c++/99283 gcc/cp/ * module.cc (dumper::operator): Make less brittle. (trees_out::core_bools): VAR_DECLs always have a context. (trees_out::key_mergeable): Use same_type_p for asserting. (trees_in::read_var_def): Propagate DECL_INITIALIZED_BY_CONSTANT_EXPRESSION_P. gcc/testsuite/ * g++.dg/modules/pr99283-5.h: New. * g++.dg/modules/pr99283-5_a.H: New. * g++.dg/modules/pr99283-5_b.H: New. * g++.dg/modules/pr99283-5_c.C: New.
next prev parent reply other threads:[~2021-03-30 16:52 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-26 8:51 [Bug c++/99283] New: " alexander.lelyakin at googlemail dot com 2021-03-05 21:06 ` [Bug c++/99283] " nathan at gcc dot gnu.org 2021-03-05 21:44 ` alexander.lelyakin at googlemail dot com 2021-03-05 23:09 ` alexander.lelyakin at googlemail dot com 2021-03-06 7:45 ` alexander.lelyakin at googlemail dot com 2021-03-13 7:07 ` alexander.lelyakin at googlemail dot com 2021-03-23 19:29 ` cvs-commit at gcc dot gnu.org 2021-03-23 19:30 ` nathan at gcc dot gnu.org 2021-03-24 6:41 ` alexander.lelyakin at googlemail dot com 2021-03-24 19:46 ` alexander.lelyakin at googlemail dot com 2021-03-26 19:08 ` cvs-commit at gcc dot gnu.org 2021-03-26 19:09 ` nathan at gcc dot gnu.org 2021-03-27 6:27 ` alexander.lelyakin at googlemail dot com 2021-03-27 18:29 ` alexander.lelyakin at googlemail dot com 2021-03-30 16:52 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-30 16:53 ` nathan at gcc dot gnu.org 2021-03-30 20:01 ` alexander.lelyakin at googlemail dot com 2021-04-01 12:37 ` cvs-commit at gcc dot gnu.org 2021-04-01 12:38 ` nathan at gcc dot gnu.org 2021-04-01 12:39 ` nathan at gcc dot gnu.org 2021-04-01 12:56 ` alexander.lelyakin at googlemail dot com 2021-04-01 13:40 ` nathan at gcc dot gnu.org 2021-04-01 13:43 ` alexander.lelyakin at googlemail dot com 2021-04-02 16:09 ` nathan at gcc dot gnu.org 2021-04-02 17:16 ` alexander.lelyakin at googlemail dot com
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-99283-4-Ap0oImktnL@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).