public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5656] testsuite: Add case-values-threshold to pr107876.C Date: Thu, 2 Feb 2023 14:53:46 +0000 (GMT) [thread overview] Message-ID: <20230202145346.37E8B3858C5F@sourceware.org> (raw) https://gcc.gnu.org/g:5b7b9d2da7691abba0a86c6e6c6935e29f365191 commit r13-5656-g5b7b9d2da7691abba0a86c6e6c6935e29f365191 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Thu Feb 2 14:53:33 2023 +0000 testsuite: Add case-values-threshold to pr107876.C This test was failing on aarch64 because aarch64 overrides TARGET_CASE_VALUES_THRESHOLD. The maximum value that allows the test to pass appears to be 6, but the default threshold is 4 or 5 (depending on whether casesi is provided). Going for 4 seemed safest, in case any target-specific features force the maximum passing threshold to be lower on some targets. gcc/testsuite/ * g++.dg/tree-ssa/pr107876.C: Add --param case-values-threshold=4. Diff: --- gcc/testsuite/g++.dg/tree-ssa/pr107876.C | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/tree-ssa/pr107876.C b/gcc/testsuite/g++.dg/tree-ssa/pr107876.C index 6cff2f1b166..d920ba050ea 100644 --- a/gcc/testsuite/g++.dg/tree-ssa/pr107876.C +++ b/gcc/testsuite/g++.dg/tree-ssa/pr107876.C @@ -1,6 +1,6 @@ // { dg-do compile } // { dg-require-effective-target c++11 } -// { dg-options "-O2 -funswitch-loops --param max-unswitch-insns=5 -fdump-tree-unswitch-details" } +// { dg-options "-O2 -funswitch-loops --param max-unswitch-insns=5 --param case-values-threshold=4 -fdump-tree-unswitch-details" } class X { public:
reply other threads:[~2023-02-02 14:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230202145346.37E8B3858C5F@sourceware.org \ --to=rsandifo@gcc.gnu.org \ --cc=gcc-cvs@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).