[Bug inline-asm/69899] gcc ICE on invalid code on x86_64-linux-gnu in "replace_reg"

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69899

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even in 3.2 I see:
/usr/src/gcc-3.2/obj/gcc/cc1 -quiet pr69899.c -m64
pr69899.c: In function `foo':
pr69899.c:2: `asm' operand requires impossible reload
pr69899.c:2: confused by earlier errors, bailing out
/usr/src/gcc-3.2/obj/gcc/cc1 -quiet pr69899.c -m32
pr69899.c: In function `foo':
pr69899.c:2: `asm' operand constraint incompatible with operand size
/usr/src/gcc-4.4/obj/gcc/cc1 -quiet pr69899.c -m64
pr69899.c: In function ‘foo’:
pr69899.c:2: error: ‘asm’ operand requires impossible reload
pr69899.c:2: confused by earlier errors, bailing out
/usr/src/gcc-4.4/obj/gcc/cc1 -quiet pr69899.c -m32
pr69899.c: In function ‘foo’:
pr69899.c:2: error: ‘asm’ operand constraint incompatible with operand size
pr69899.c:2: error: ‘asm’ operand has impossible constraints
So at least for -m64 this is not a regression (well, to some extent a
regression from error-recovery ICE to normal ice-on-invalid-code).
For -m32, the behavior changed with r192719 aka when LRA has been added.