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++/106363] [13/14 Regression] [modules] ICE using-declaration of imported name in the same namespace Date: Sat, 16 Dec 2023 23:39:18 +0000 [thread overview] Message-ID: <bug-106363-4-B3tUKolEFH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106363-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106363 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>: https://gcc.gnu.org/g:cb76f46c97e9f4e4869acceb77a000b6cc2cda0e commit r14-6636-gcb76f46c97e9f4e4869acceb77a000b6cc2cda0e Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Sun Nov 12 11:54:43 2023 +1100 c++: Seed namespaces for bindings [PR106363] Currently the first depset for an EK_BINDING is not seeded. This breaks the attached testcase as then the namespace is not considered referenced yet during streaming, but we've already finished importing. There doesn't seem to be any particular reason I could find for skipping the first depset for bindings, and removing the condition doesn't appear to cause any test failures, so this patch removes that check. PR c++/106363 gcc/cp/ChangeLog: * module.cc (module_state::write_cluster): Don't skip first depset for bindings. gcc/testsuite/ChangeLog: * g++.dg/modules/pr106363_a.C: New test. * g++.dg/modules/pr106363_b.C: New test. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
next prev parent reply other threads:[~2023-12-16 23:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-20 2:07 [Bug c++/106363] New: [modules] Can't selectively reexport imported declaration in " johelegp at gmail dot com 2022-10-24 19:53 ` [Bug c++/106363] [13 Regression] " johelegp at gmail dot com 2022-10-24 20:07 ` [Bug c++/106363] [13 Regression] [modules] ICE using-declaration of imported name in the " johelegp at gmail dot com 2022-11-29 16:48 ` pinskia at gcc dot gnu.org 2022-12-22 14:57 ` rguenth at gcc dot gnu.org 2023-04-26 6:56 ` [Bug c++/106363] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2023-12-16 23:39 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-10 3:28 ` [Bug c++/106363] [13 " law at gcc dot gnu.org 2024-03-13 17:48 ` ppalka 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-106363-4-B3tUKolEFH@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).