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 target/113175] New: [14 Regression] MMIX: testsuite/std/ranges/iota/max_size_type.cc 5x times slower Date: Sat, 30 Dec 2023 00:36:22 +0000 [thread overview] Message-ID: <bug-113175-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113175 Bug ID: 113175 Summary: [14 Regression] MMIX: testsuite/std/ranges/iota/max_size_type.cc 5x times slower Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org Target Milestone: --- Host: x86_64-linux-gnu Target: mmix-knuth-mmixware (Perhaps a "[13 Regression]" as well - haven't checked.) I ran the testsuite for mmix-knuth-mmixware (a 64-bit newlib cross) and found that testsuite/std/ranges/iota/max_size_type.cc times out, despite the timeout-factor increased by a factor 4 (from 360 seconds to 1440 seconds) in r12-2799-ge9b639c4b53221. For a tree at r12-2797-g307e0d40367996 running this test takes 11:43.61 (mm:ss) wall-clock time and now at r14-6859-gd1eacedc6d9b it takes 58:45.78 (on one and the same host and same session within the same hour; no host-side changes and the test itself apparently hasn't changed significantly). I haven't checked whether this affects other targets, but if so, a 5x performance regression should have been picked up by other testers, thus I'm starting with "target" until firther investigated.
next reply other threads:[~2023-12-30 0:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 0:36 hp at gcc dot gnu.org [this message] 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 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@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).