public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104345] [12 Regression] "nvptx: Transition nvptx backend to STORE_FLAG_VALUE = 1" patch made some code generation worse Date: Tue, 08 Feb 2022 12:33:03 +0000 [thread overview] Message-ID: <bug-104345-4-SS6nIiaypA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104345-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104345 --- Comment #8 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Well. Here's another problem. Re-testing things using a "bad" '__muldc3' from a build with your three patches applied, I notice that my '_muldc3-WIP.o' "old"/replacement code uses a 'set.u32.leu.f64', 'neg.s32', 'mov.u32' sequence. That works. However, if I replace that with a localized (its own '.reg .pred %r138_;') 'setp.leu.f64', 'selp.u32' sequence (as per your code generation changes), then it doesn't in fact work! Huh. Will later continue looking into this.
next prev parent reply other threads:[~2022-02-08 12:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-02 14:10 [Bug target/104345] New: nvptx: "regression" after "nvptx: Transition nvptx backend to STORE_FLAG_VALUE = 1" tschwinge at gcc dot gnu.org 2022-02-02 14:26 ` [Bug target/104345] " roger at nextmovesoftware dot com 2022-02-02 22:37 ` [Bug target/104345] [12 Regression] "nvptx: Transition nvptx backend to STORE_FLAG_VALUE = 1" patch made some code generation worse pinskia at gcc dot gnu.org 2022-02-03 14:17 ` vries at gcc dot gnu.org 2022-02-03 21:09 ` roger at nextmovesoftware dot com 2022-02-08 11:53 ` tschwinge at gcc dot gnu.org 2022-02-08 11:54 ` tschwinge at gcc dot gnu.org 2022-02-08 11:55 ` tschwinge at gcc dot gnu.org 2022-02-08 11:57 ` tschwinge at gcc dot gnu.org 2022-02-08 12:33 ` tschwinge at gcc dot gnu.org [this message] 2022-02-08 15:36 ` tschwinge at gcc dot gnu.org 2022-02-10 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-10 8:02 ` cvs-commit at gcc dot gnu.org 2022-03-02 12:10 ` roger at nextmovesoftware 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-104345-4-SS6nIiaypA@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).