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 testsuite/113175] [11/12/13/14 Regression] testsuite/std/ranges/iota/max_size_type.cc 5x times slower Date: Wed, 03 Jan 2024 16:00:58 +0000 [thread overview] Message-ID: <bug-113175-4-wIw0usoOGC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113175-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113175 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:1fb2b5c9a7fb212a5936cc702e49175ef988e5ad commit r12-10079-g1fb2b5c9a7fb212a5936cc702e49175ef988e5ad Author: Patrick Palka <ppalka@redhat.com> Date: Tue Jan 2 21:31:20 2024 -0500 libstdc++: testsuite: Reduce max_size_type.cc exec time [PR113175] The adjustment to max_size_type.cc in r14-205-g83470a5cd4c3d2 inadvertently increased the execution time of this test by over 5x due to making the two main loops actually run in the signed_p case instead of being dead code. To compensate, this patch cuts the relevant loops' range [-1000,1000] by 10x as proposed in the PR. This shouldn't significantly weaken the test since the same important edge cases are still checked in the smaller range and/or elsewhere. On my machine this reduces the test's execution time by roughly 10x (and 1.6x relative to before r14-205). PR testsuite/113175 libstdc++-v3/ChangeLog: * testsuite/std/ranges/iota/max_size_type.cc (test02): Reduce 'limit' to 100 from 1000 and adjust 'log2_limit' accordingly. (test03): Likewise. (cherry picked from commit a138b99646a5551c53b860648521adb5bfe8c2fa)
next prev parent reply other threads:[~2024-01-03 16:00 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 0:36 [Bug target/113175] New: [14 Regression] MMIX: " hp at gcc dot gnu.org 2023-12-30 18:01 ` [Bug libstdc++/113175] [14 Regression] " hp at gcc dot gnu.org 2023-12-30 22:48 ` hp at gcc dot gnu.org 2023-12-31 16:49 ` [Bug testsuite/113175] " hp at gcc dot gnu.org 2023-12-31 17:08 ` xry111 at gcc dot gnu.org 2023-12-31 17:16 ` hp at gcc dot gnu.org 2023-12-31 21:47 ` redi at gcc dot gnu.org 2023-12-31 21:52 ` redi at gcc dot gnu.org 2024-01-02 17:06 ` [Bug testsuite/113175] [11/12/13/14 " ppalka at gcc dot gnu.org 2024-01-02 17:21 ` ppalka at gcc dot gnu.org 2024-01-03 2:31 ` cvs-commit at gcc dot gnu.org 2024-01-03 15:29 ` cvs-commit at gcc dot gnu.org 2024-01-03 16:00 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-03 16:04 ` cvs-commit at gcc dot gnu.org 2024-01-03 16:04 ` 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-113175-4-wIw0usoOGC@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).