public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "inform at tiker dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107127] New: [Regression 11/12] Long compile times on code with C complex Date: Mon, 03 Oct 2022 02:03:23 +0000 [thread overview] Message-ID: <bug-107127-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127 Bug ID: 107127 Summary: [Regression 11/12] Long compile times on code with C complex Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: inform at tiker dot net Target Milestone: --- A generated code using C-style complex arithmetic that compiled nearly instantaneously with gcc 10.4 takes >=30s with gcc 11.3.0 and 12.2.0. How to reproduce: git clone https://gist.github.com/inducer/802e227e86e3ff4fd95aa0fefae462fe.git cd 802e227e86e3ff4fd95aa0fefae462fe git checkout 9eb600e $ time gcc-10 -c post-110.c gcc-10 -c post-110.c 0,05s user 0,02s system 45% cpu 0,155 total $ time gcc-11 -c post-110.c ^C gcc-11 -c post-110.c 0,00s user 0,00s system 0% cpu 23,757 total $ time gcc-12 -c post-110.c ^C gcc-12 -c post-110.c 0,00s user 0,00s system 0% cpu 31,574 total This does not seem to be very sensitive to headers, so I'm not including preprocessed source to start. Happy to supply it if needed. Target: x86_64-linux-gnu Precise versions: gcc version 10.4.0 (Debian 10.4.0-5) gcc version 11.3.0 (Debian 11.3.0-5) gcc version 12.2.0 (Debian 12.2.0-3) x-ref: https://github.com/inducer/loopy/issues/686
next reply other threads:[~2022-10-03 2:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-03 2:03 inform at tiker dot net [this message] 2022-10-03 9:31 ` [Bug c/107127] [11/12/13 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363 marxin at gcc dot gnu.org 2022-10-03 9:53 ` marxin at gcc dot gnu.org 2022-10-03 19:49 ` pinskia at gcc dot gnu.org 2022-10-03 19:52 ` pinskia at gcc dot gnu.org 2022-10-06 9:59 ` rguenth at gcc dot gnu.org 2022-11-22 11:10 ` jakub at gcc dot gnu.org 2022-11-23 18:10 ` cvs-commit at gcc dot gnu.org 2022-11-23 18:11 ` [Bug c/107127] [11/12 " jakub at gcc dot gnu.org 2022-11-24 9:34 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:43 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:57 ` [Bug c/107127] [11 " jakub at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 9:29 ` jakub 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-107127-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).