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 rtl-optimization/92151] Spurious register copying
Date: Tue, 27 Jun 2023 03:54:29 +0000 [thread overview]
Message-ID: <bug-92151-4-8OZZog1H8I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92151-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92151
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #3)
>
> Here's a manually reduced variant that exhibits a similar issue at -O1:
>
> void foo(int num, int c) {
> asm("# %0" : "+r"(num));
> while (--c)
> asm goto("# %0" :: "r"(num) :: l2);
> l2:
> asm("# %0" :: "r"(num));
> }
Note the DEAD_REG is updated in IRA anyways so that is not the issue.
This reduced testcase seems to be fixed in GCC 11+, maybe r11-209
(https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545442.html).
The original testcase did fix on mov issue.
But
__asm__("\t mov %q[w], (%q[d])\n" // write
: "=m" (*d) : [d] "r" (d), [w] "r" (w)) ;
__asm__("\t lea 8(%q[d]), %q[d]\n"
: [d] "+r" (d)) ;
Still causes an extra move to happen.
Note there was one improvement in GCC 11 in the original testcase too.
I think TWITCH difference is due to the way register variables are represented
in gimple ...
parent reply other threads:[~2023-06-27 3:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-92151-4@http.gcc.gnu.org/bugzilla/>]
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-92151-4-8OZZog1H8I@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: link
Be 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).