https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #8 from Hongtao.liu ---
> But, if you're going to improve constant generation, please make it so that
> it can recognize not only the particular pattern described in this bug. More
> importantly, it should recognize the all-ones cas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #7 from andysem at mail dot ru ---
To be clear, I'm not asking the compiler to recognize the particular pattern of
alternating 0x00 and 0xFF bytes. Because hardcoding this particular pattern
won't improve generated code in other cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #6 from andysem at mail dot ru ---
(In reply to Andrew Pinski from comment #1)
> >and gcc 12 generates a worse code:
>
> it is not worse really; depending on the how fast moving between the
> register sets is.
I meant "worse" compar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-01-16
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #2 from Andrew Pinski ---
r12-1958-gedafb35bdadf30 changed the behavior in GCC 12 to be better ...
(see the commit message that it shows it is better than doing a memory load).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #1 from Andrew Pinski ---
>and gcc 12 generates a worse code:
it is not worse really; depending on the how fast moving between the register
sets is.
