https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88414
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
On 10.x and 9.x with checking enabled
The test case for this produces the following output for i686-apple-darwin9
(actually any Darwin N from 9 - 17).
/src-local/gcc-master/gcc/testsuite/gcc.target/i386/pr88414.c:15:7: error:
‘asm’ operand has impossible constraints
15 | asm volatile ("" : "=d" (b), "=d" (c) : "r" (y[j]), "d" (w)); /*
{ dg-error "'asm' operand has impossible constraints" } */
| ^~~
during RTL pass: reload
/src-local/gcc-master/gcc/testsuite/gcc.target/i386/pr88414.c:25:1: internal
compiler error: maximum number of LRA assignment passes is achieved (30)
25 | }
| ^
** when checking is disabled (i.e. set to release) the case hangs (which hangs
the test suite). **
>From 11.x+ the diagnostic is emitted and the test case finishes OK.
This is the patch that 'fixes' this:
r11-209-g74dc179a6da33cd00f6d4a93fbb97dc84f610126
Would it. or some equivalent, be appropriate for 10.4? (since IMO a hang is
less user-friendly than an ICE) - of course, the code is invalid either way ...
