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/102971] GCC cannot understand >>32 pattern Date: Thu, 28 Oct 2021 08:19:21 +0000 [thread overview] Message-ID: <bug-102971-4-dUu8FBAYn8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102971-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102971 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|middle-end |target Target|i?86 |i?86-*-* Status|UNCONFIRMED |NEW Last reconfirmed| |2021-10-28 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. With -mno-stv the assembly looks much better so something is wrong there with costing when deciding to do 64bit math in SSE regs as opposed to GPR pairs.
prev parent reply other threads:[~2021-10-28 8:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-27 20:29 [Bug tree-optimization/102971] New: " unlvsur at live dot com 2021-10-27 20:30 ` [Bug tree-optimization/102971] " unlvsur at live dot com 2021-10-27 21:03 ` pinskia at gcc dot gnu.org 2021-10-28 8:19 ` 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-102971-4-dUu8FBAYn8@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).