public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-9055] testsuite: Mark non-optimized variants as expensive Date: Sun, 18 Feb 2024 10:06:58 +0000 (GMT) [thread overview] Message-ID: <20240218100658.E70A03858D20@sourceware.org> (raw) https://gcc.gnu.org/g:3796216bfa49b5ca288afe0760931a4c5b8ea346 commit r14-9055-g3796216bfa49b5ca288afe0760931a4c5b8ea346 Author: Dimitar Dimitrov <dimitar@dinux.eu> Date: Thu Feb 15 21:02:37 2024 +0200 testsuite: Mark non-optimized variants as expensive When not optimized for speed, the test for PR112344 takes several seconds to execute on native x86_64, and 15 minutes on PRU target simulator. Thus mark those variants as expensive. The -O2 variant which originally triggered the PR is not expensive, hence it is still run by default. PR middle-end/112344 gcc/testsuite/ChangeLog: * gcc.dg/torture/pr112344.c: Run non-optimized variants only if expensive tests are allowed. Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu> Diff: --- gcc/testsuite/gcc.dg/torture/pr112344.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.dg/torture/pr112344.c b/gcc/testsuite/gcc.dg/torture/pr112344.c index c52d2c8304ba..657322caed07 100644 --- a/gcc/testsuite/gcc.dg/torture/pr112344.c +++ b/gcc/testsuite/gcc.dg/torture/pr112344.c @@ -1,5 +1,6 @@ /* { dg-do run } */ /* { dg-require-effective-target int32plus } */ +/* { dg-skip-if "non-optimized code is too slow" { ! run_expensive_tests } { "*" } { "-O2" "-O3" } } */ int main ()
reply other threads:[~2024-02-18 10:06 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=20240218100658.E70A03858D20@sourceware.org \ --to=dimitar@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).