From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++/modules testsuite: avoid expensive ggc-min-expand=0
Date: Wed, 24 Apr 2024 09:59:12 -0400 [thread overview]
Message-ID: <7c413266-3b5d-4f47-bd8d-be28eb25939e@redhat.com> (raw)
In-Reply-To: <2db46b9e-891b-39cd-31ff-8e5214743b54@idea>
On 4/24/24 05:49, Patrick Palka wrote:
> On Tue, 23 Apr 2024, Jason Merrill wrote:
>
>> On 4/23/24 11:28, Patrick Palka wrote:
>>> Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
>>
>> Is the test being run for multiple standard levels? I'd rather restrict it to
>> one and keep fully testing GC-safety.
>
> Ah yeah, looks like it runs three times by default, in C++17, C++20 and
> C++23 mode. Like so? The speedup is almost as good as using
> ggc-min-expand=1.
OK.
> Interestingly, restricting to one standard level _and_ using
> ggc-min-expand=1 does not give further speedup.
>
> -- >8 --
>
> Subject: [PATCH] c++/modules testsuite: restrict expensive pr99023 test
>
> The pr99023 testcase uses --param=ggc-min-expand=0 which forces a GC
> during every collection point and consequently is very slow to run,
> and ends up being the main bottleneck of the modules.exp testsuite.
>
> So this patch restricts this test to run once, in C++20 mode, instead of
> multiple times (C++17, C++20 and C++23 mode by default). After this
> patch the modules.exp testsuite finishes in 3m instead of 3m40s with -j8
> on my machine.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/modules/pr99023_a.X: Run only in C++20 mode.
> * g++.dg/modules/pr99023_b.X: Likewise.
> ---
> gcc/testsuite/g++.dg/modules/pr99023_a.X | 1 +
> gcc/testsuite/g++.dg/modules/pr99023_b.X | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/gcc/testsuite/g++.dg/modules/pr99023_a.X b/gcc/testsuite/g++.dg/modules/pr99023_a.X
> index c872d15f792..507e9569535 100644
> --- a/gcc/testsuite/g++.dg/modules/pr99023_a.X
> +++ b/gcc/testsuite/g++.dg/modules/pr99023_a.X
> @@ -1,4 +1,5 @@
> // PR c++/99023, ICE
> +// { dg-require-effective-target c++20_only }
> // { dg-additional-options {-x c++-system-header initializer_list -fmodules-ts --param ggc-min-expand=0} }
>
> // { dg-prune-output {linker input file unused} }
> diff --git a/gcc/testsuite/g++.dg/modules/pr99023_b.X b/gcc/testsuite/g++.dg/modules/pr99023_b.X
> index ca5f32e5bcc..59d32bee8d5 100644
> --- a/gcc/testsuite/g++.dg/modules/pr99023_b.X
> +++ b/gcc/testsuite/g++.dg/modules/pr99023_b.X
> @@ -1,4 +1,5 @@
> // PR c++/99023, ICE
> +// { dg-require-effective-target c++20_only }
> // { dg-additional-options {-x c++-system-header iostream -fmodules-ts -flang-info-include-translate=<initializer_list> --param ggc-min-expand=0} }
>
> // { dg-prune-output {linker input file unused} }
prev parent reply other threads:[~2024-04-24 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:28 Patrick Palka
2024-04-23 20:02 ` Jason Merrill
2024-04-24 12:49 ` Patrick Palka
2024-04-24 13:59 ` Jason Merrill [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=7c413266-3b5d-4f47-bd8d-be28eb25939e@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ppalka@redhat.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).