From: Nathan Sidwell <nathan@acm.org>
To: Nathaniel Shead <nathanieloshead@gmail.com>, gcc-patches@gcc.gnu.org
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] c++/modules: seed namespaces for bindings [PR106363]
Date: Sat, 6 Jan 2024 17:23:07 -0500 [thread overview]
Message-ID: <1739da56-c77d-4c97-a324-366e64a73820@acm.org> (raw)
In-Reply-To: <6550318c.170a0220.caf0c.3fe5@mx.google.com>
Ok,
I think I js=ust thought this unnecessary.
On 11/11/23 20:59, Nathaniel Shead wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu. I don't have write
> access.
>
> -- >8 --
>
> 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>
> ---
> gcc/cp/module.cc | 4 +---
> gcc/testsuite/g++.dg/modules/pr106363_a.C | 9 +++++++++
> gcc/testsuite/g++.dg/modules/pr106363_b.C | 10 ++++++++++
> 3 files changed, 20 insertions(+), 3 deletions(-)
> create mode 100644 gcc/testsuite/g++.dg/modules/pr106363_a.C
> create mode 100644 gcc/testsuite/g++.dg/modules/pr106363_b.C
>
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index c1c8c226bc1..411a3b9411c 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -14741,9 +14741,7 @@ module_state::write_cluster (elf_out *to, depset *scc[], unsigned size,
> for (unsigned ix = 0; ix != size; ix++)
> {
> depset *b = scc[ix];
> - for (unsigned jx = (b->get_entity_kind () == depset::EK_BINDING
> - || b->is_special ()) ? 1 : 0;
> - jx != b->deps.length (); jx++)
> + for (unsigned jx = b->is_special (); jx != b->deps.length (); jx++)
> {
> depset *dep = b->deps[jx];
>
> diff --git a/gcc/testsuite/g++.dg/modules/pr106363_a.C b/gcc/testsuite/g++.dg/modules/pr106363_a.C
> new file mode 100644
> index 00000000000..c18d2eef1c8
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/modules/pr106363_a.C
> @@ -0,0 +1,9 @@
> +// PR c++/106363
> +// { dg-additional-options "-fmodules-ts" }
> +// { dg-module-cmi pr106363.a }
> +
> +export module pr106363.a;
> +
> +namespace ns {
> + export int x;
> +}
> diff --git a/gcc/testsuite/g++.dg/modules/pr106363_b.C b/gcc/testsuite/g++.dg/modules/pr106363_b.C
> new file mode 100644
> index 00000000000..0508c0d6193
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/modules/pr106363_b.C
> @@ -0,0 +1,10 @@
> +// PR c++/106363
> +// { dg-additional-options "-fmodules-ts" }
> +// { dg-module-cmi pr106363.b }
> +
> +export module pr106363.b;
> +import pr106363.a;
> +
> +namespace ns {
> + export using ns::x;
> +}
--
Nathan Sidwell
prev parent reply other threads:[~2024-01-06 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 1:59 Nathaniel Shead
2023-12-16 10:31 ` Nathaniel Shead
2023-12-16 23:19 ` Nathan Sidwell
2024-01-06 22:23 ` Nathan Sidwell [this message]
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=1739da56-c77d-4c97-a324-366e64a73820@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathanieloshead@gmail.com \
/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).