public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/113175] [14 Regression] testsuite/std/ranges/iota/max_size_type.cc 5x times slower Date: Sun, 31 Dec 2023 16:49:08 +0000 [thread overview] Message-ID: <bug-113175-4-7j0B9oTcO1@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 Hans-Peter Nilsson <hp at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libstdc++ |testsuite --- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- There's one single regression event, bringing the host runtime to about 1.63 seconds. Then some time later, an additional 0.1 second was added (accumulated). I did not look into that latter regression. The big one is clouded by a large range of commits where max_size_type failed, due to r14-159-g03cebd304955a6. This was fixed in r14-205-g83470a5cd4c3d2, at which time there the big regression is seen for the first time. That is also the "cause" for the commit, because applying that commit to r14-158-g7d115e01411156 shows the same number as for r14-205-g83470a5cd4c3d2. Actually, it's the testsuite part of that patch, because with that reverted the execution time backs down to 0.33 seconds. IOW, this while PR is /testsuites. Not sure what to do to improve the execution time, as plain disabling the using "signed_rep_t = __int128;" by making the first line "+#if 0 && __SIZEOF_INT128__" yields /x/testsuite/std/ranges/iota/max_size_type.cc:36: note: the comparison reduces to '(16 == 8)' Maybe the higher number for the execution time is actually the "right" one and the range should be cut down to -100..100 for *all* targets? HNY!
next prev parent reply other threads:[~2023-12-31 16:49 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 ` hp at gcc dot gnu.org [this message] 2023-12-31 17:08 ` [Bug testsuite/113175] " 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 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-7j0B9oTcO1@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).