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/95083] x86 fp_movcc expansion depends on real_cst sharing Date: Thu, 20 Jul 2023 08:42:18 +0000 [thread overview] Message-ID: <bug-95083-4-OBLNDScYLq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95083-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95083 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed with the fix for PR61747. Since min/max requires equal constants and they are now pushed to a common reg I'm not sure we need any such new patterns. Maybe with integer min/max.
prev parent reply other threads:[~2023-07-20 8:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-12 13:41 [Bug target/95083] New: " rguenth at gcc dot gnu.org 2020-05-12 13:42 ` [Bug target/95083] " rguenth at gcc dot gnu.org 2020-05-13 14:13 ` ubizjak at gmail dot com 2023-07-20 8:42 ` rguenth 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-95083-4-OBLNDScYLq@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).