https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105032
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-03-23
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
CC| |jakub at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This has been hanging or ICEing on and off since forever.
E.g. even r105000 ICEs, r200000 works, r210000 ICEs, r10-5912 works, r11-1
hangs, so does current trunk.
The first revision after r10-5912 to start hanging was
r10-6326-gbcf3fa7cf5a3d024b507.
Note, without optimizations, the inline asm is on or beyond the border what can
be handled, it uses 6 of the 8 GPRs the arch has, the further two are the stack
pointer and when not optimizing or if frame pointer is for whatever reason
needed frame pointer. The asm also has a memory input. So, it fully depends
on optimization (which isn't done with -O0 generally) that the address of the
_arg6 variable can be expressed as offset(%esp) or offset(%ebp). If it is not
(and -O0 asks for no optimizations), then there are no registers left how to
describe the input.
