public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102947] SPEC2006 compiler time regression (-Ofast -march=native -flto) between 1932e1169a236849 and 9cfb95f9b92326e8 Date: Tue, 26 Oct 2021 14:49:47 +0000 [thread overview] Message-ID: <bug-102947-4-UmsCk9Vnow@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102947-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102947 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-10-26 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks| |26163 CC| |marxin at gcc dot gnu.org --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Yes, I can confirm also other testers reports slower compilation of WRF: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=2.270.8 I know the benchmark contains a huge config module that delays the compilation rapidly. Moreover, one ltrans always runs much longer than the others. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 [Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
next prev parent reply other threads:[~2021-10-26 14:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 14:42 [Bug middle-end/102947] New: " hubicka at gcc dot gnu.org 2021-10-26 14:47 ` [Bug middle-end/102947] " hubicka at gcc dot gnu.org 2021-10-26 14:49 ` marxin at gcc dot gnu.org [this message] 2021-10-26 14:53 ` [Bug middle-end/102947] SPEC2006 481.wrf compiler time regression (-Ofast -march=native -flto) between g:1932e1169a236849 and g:9cfb95f9b92326e8 marxin at gcc dot gnu.org 2021-10-26 14:57 ` pinskia 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-102947-4-UmsCk9Vnow@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).