public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105157] [12 Regression] compile-time regressions with generic tuning since r12-7756-g27d8748df59fe6 Date: Fri, 08 Apr 2022 14:16:34 +0000 [thread overview] Message-ID: <bug-105157-4-cSp5CHGa4t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105157-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105157 avieira at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from avieira at gcc dot gnu.org --- The commit above should have fixed the issue. Let me know if you still observe the higher compile-time in your nightlies.
prev parent reply other threads:[~2022-04-08 14:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 9:50 [Bug target/105157] New: [12 Regression] compile-time regressions with generic tuning rguenth at gcc dot gnu.org 2022-04-05 9:53 ` [Bug target/105157] " rguenth at gcc dot gnu.org 2022-04-06 8:35 ` marxin at gcc dot gnu.org 2022-04-06 10:57 ` [Bug target/105157] [12 Regression] compile-time regressions with generic tuning since r12-7756-g27d8748df59fe6 marxin at gcc dot gnu.org 2022-04-06 10:57 ` marxin at gcc dot gnu.org 2022-04-06 11:05 ` marxin at gcc dot gnu.org 2022-04-06 11:13 ` rguenth at gcc dot gnu.org 2022-04-06 11:21 ` tnfchris at gcc dot gnu.org 2022-04-06 11:29 ` rguenth at gcc dot gnu.org 2022-04-06 17:24 ` avieira at gcc dot gnu.org 2022-04-08 14:15 ` cvs-commit at gcc dot gnu.org 2022-04-08 14:16 ` avieira at gcc dot gnu.org [this message]
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-105157-4-cSp5CHGa4t@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).