public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103423] New: 19% cpu2006 wrf compile time regression with -flto between g:0b7a11874d4eb428 and g:704e8a825c78b9a8 Date: Thu, 25 Nov 2021 08:43:29 +0000 [thread overview] Message-ID: <bug-103423-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103423 Bug ID: 103423 Summary: 19% cpu2006 wrf compile time regression with -flto between g:0b7a11874d4eb428 and g:704e8a825c78b9a8 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org Target Milestone: --- This is visible at: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=427.270.8&plot.1=227.270.8& https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=413.270.8&plot.1=292.270.8& https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=412.270.8&plot.1=289.270.8& https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=445.270.8&plot.1=233.270.8& Curiously it does not seem to show on 2017 version of wrf.
next reply other threads:[~2021-11-25 8:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-25 8:43 hubicka at gcc dot gnu.org [this message] 2021-11-25 9:35 ` [Bug tree-optimization/103423] [12 Regression] 19% cpu2006 wrf compile time regression with -flto since r12-3903-g0288527f47cec669 marxin at gcc dot gnu.org 2021-11-25 22:17 ` hubicka at kam dot mff.cuni.cz 2021-11-26 8:58 ` [Bug tree-optimization/103423] [12 Regression] 19% cpu2006 wrf compile time regression with -flto since r12-2353-g8da8ed435e9f01b3 marxin at gcc dot gnu.org 2021-11-26 9:12 ` hubicka at kam dot mff.cuni.cz 2021-11-26 9:18 ` marxin at gcc dot gnu.org 2022-01-18 14:15 ` rguenth at gcc dot gnu.org 2022-01-18 14:27 ` hubicka at kam dot mff.cuni.cz
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-103423-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).