https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
Stas Sergeev changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
--- Comment #5 from Andrew Pinski ---
(In reply to Stas Sergeev from comment #4)
> Would it be possible to at least show the
> correct line number where the register allocation
> actually failed? gcc points to a rather "random"
> line
Hmm, getti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
--- Comment #4 from Stas Sergeev ---
Would it be possible to at least show the
correct line number where the register allocation
actually failed? gcc points to a rather "random"
line, and it required many hours of an engineer
work to find the pro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
--- Comment #3 from Jakub Jelinek ---
If you are using inline asm, you need to know what you are doing.
https://gcc.gnu.org/onlinedocs/gcc-8.2.0/gcc/Simple-Constraints.html#Simple-Constraints
‘r’
A register operand is allowed provided that it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
--- Comment #2 from Stas Sergeev ---
(In reply to Jakub Jelinek from comment #1)
> the same for -m64, but only al/bl/cl/dl for -m32, because there is no
> sil/dil/bpl for -m32.
But why does this matter?
I am perfectly fine with al/bl/cl/dl, neve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89334
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
