public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103316] PowerPC: Gimple folding of int128 comparisons produces suboptimal code Date: Fri, 19 Nov 2021 14:12:20 +0000 [thread overview] Message-ID: <bug-103316-4-n8GcBdae2u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103316 --- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> --- Ah, now I see. Thanks! Power10 has some new 128-bit insns (and p9 and p8 did before, too). I still think it would be best if Gimple did *never* split data. It simply does not know enough about the machine and what the eventual machine code will be like to do so advantageously. This is the kind of thing that RTL can do much better, is much better positioned to do (and in fact it does do this, in all subregN passes).
next prev parent reply other threads:[~2021-11-19 14:12 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 15:59 [Bug target/103316] New: " wschmidt at gcc dot gnu.org 2021-11-18 16:00 ` [Bug target/103316] " wschmidt at gcc dot gnu.org 2021-11-19 7:35 ` rguenth at gcc dot gnu.org 2021-11-19 8:19 ` segher at gcc dot gnu.org 2021-11-19 13:53 ` wschmidt at gcc dot gnu.org 2021-11-19 13:54 ` wschmidt at gcc dot gnu.org 2021-11-19 14:07 ` wschmidt at gcc dot gnu.org 2021-11-19 14:12 ` segher at gcc dot gnu.org [this message] 2021-11-19 14:19 ` rguenth at gcc dot gnu.org 2021-11-19 14:21 ` segher at gcc dot gnu.org 2021-11-19 14:23 ` segher at gcc dot gnu.org 2021-11-19 17:09 ` wschmidt at gcc dot gnu.org 2021-11-19 17:11 ` wschmidt at gcc dot gnu.org 2021-11-19 17:34 ` segher at gcc dot gnu.org 2021-11-19 17:36 ` segher at gcc dot gnu.org 2021-11-19 17:42 ` wschmidt at gcc dot gnu.org 2022-03-07 2:24 ` guihaoc at gcc dot gnu.org 2022-03-07 20:07 ` segher at gcc dot gnu.org 2022-06-16 8:59 ` cvs-commit at gcc dot gnu.org 2022-06-16 9:02 ` guihaoc 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-103316-4-n8GcBdae2u@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).