https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Richard Biener changed:
What|Removed |Added
Target Milestone|9.5 |---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Richard Biener changed:
What|Removed |Added
Target Milestone|9.4 |9.5
--- Comment #7 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.3 |9.4
--- Comment #6 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.2 |9.3
--- Comment #5 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.0 |9.2
--- Comment #4 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
--- Comment #3 from Nicholas Piggin ---
(In reply to Segher Boessenkool from comment #2)
> If you want some specific machine code for something complex like this, it
> is much easier to write the machine code than to fight the compiler.
Yes, und
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
--- Comment #2 from Segher Boessenkool ---
If you want some specific machine code for something complex like this, it
is much easier to write the machine code than to fight the compiler.
That said:
1) "flags" is stored in the same register ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84443
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Target|