public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40730] redundant memory load Date: Mon, 15 May 2023 00:10:08 +0000 [thread overview] Message-ID: <bug-40730-4-p1Y7l29Q0Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40730 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=33315 Known to fail| |10.1.0, 11.1.0, 5.1.0 Known to work| |12.1.0, 13.1.0 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #14 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed for GCC 12 by r12-897-gde56f95afaaa22 (and r11-408-g84935c9822183c).
next parent reply other threads:[~2023-05-15 0:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40730-4@http.gcc.gnu.org/bugzilla/> 2023-05-15 0:10 ` pinskia at gcc dot gnu.org [this message] 2023-05-15 0:24 ` pinskia at gcc dot gnu.org 2009-07-13 8:57 [Bug target/40730] New: " carrot at google dot com 2009-07-13 8:58 ` [Bug target/40730] " carrot at google dot com 2009-07-13 9:51 ` rguenth at gcc dot gnu dot org 2009-07-13 10:10 ` steven at gcc dot gnu dot org 2009-07-14 9:14 ` carrot at google dot com 2009-07-14 9:18 ` steven at gcc dot gnu dot org 2009-07-14 9:20 ` steven at gcc dot gnu dot org 2009-07-15 8:07 ` carrot at google dot com 2009-07-15 9:47 ` steven at gcc dot gnu dot org 2010-01-08 9:34 ` steven at gcc dot gnu dot org 2010-01-11 6:47 ` carrot at google dot com 2010-01-11 8:23 ` stevenb dot gcc at gmail dot com 2010-01-11 8:56 ` carrot at google dot com
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-40730-4-p1Y7l29Q0Z@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).