public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104912] [12 Regression] 416.gamess regression after r12-7612 Date: Mon, 14 Mar 2022 11:06:47 +0000 [thread overview] Message-ID: <bug-104912-4-9i0cyG3yKT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104912 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Target| |x86_64-*-* Target Milestone|--- |12.0 Blocks| |26163 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:[~2022-03-14 11:06 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-14 11:06 [Bug target/104912] New: " rguenth at gcc dot gnu.org 2022-03-14 11:06 ` rguenth at gcc dot gnu.org [this message] 2022-03-14 11:55 ` [Bug target/104912] [12 Regression] 416.gamess regression after r12-7612-g69619acd8d9b58 rguenth at gcc dot gnu.org 2022-03-14 11:58 ` rguenth at gcc dot gnu.org 2022-03-14 12:17 ` rguenth at gcc dot gnu.org 2022-03-14 13:49 ` rguenth at gcc dot gnu.org 2022-03-14 14:25 ` rguenth at gcc dot gnu.org 2022-03-17 12:31 ` rguenth at gcc dot gnu.org 2022-03-21 13:08 ` rguenth at gcc dot gnu.org 2022-04-13 7:54 ` cvs-commit at gcc dot gnu.org 2022-04-13 8:02 ` rguenth at gcc dot gnu.org 2022-04-20 11:28 ` cvs-commit at gcc dot gnu.org 2022-05-06 8:33 ` [Bug target/104912] [12/13 " jakub at gcc dot gnu.org 2022-07-26 12:42 ` rguenth at gcc dot gnu.org 2023-01-31 11:22 ` jamborm at gcc dot gnu.org 2023-01-31 12:02 ` rguenth at gcc dot gnu.org 2023-05-08 12:24 ` [Bug target/104912] [12/13/14 " rguenth 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-104912-4-9i0cyG3yKT@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).