public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug rtl-optimization/92151] Spurious register copying
[not found] <bug-92151-4@http.gcc.gnu.org/bugzilla/>
@ 2023-06-27 3:54 ` pinskia at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: pinskia at gcc dot gnu.org @ 2023-06-27 3:54 UTC (permalink / raw)
To: gcc-bugs
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 ...
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-27 3:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-92151-4@http.gcc.gnu.org/bugzilla/>
2023-06-27 3:54 ` [Bug rtl-optimization/92151] Spurious register copying pinskia at gcc dot gnu.org
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).