On Fri, 11 Jan 2013, Andreas Schwab wrote:
> Jakub Jelinek writes:
>
> > + __asm ("" : "=r" (cf) : "0" (ucf1.ll));
>
> gcc/testsuite/gcc.c-torture/compile/pr55921.c:17:3: error: 'asm' operand has
> impossible constraints
> gcc/testsuite/gcc.c-torture/compile/pr55921.c:19:3: error: 'asm' opera
Jakub Jelinek writes:
> + __asm ("" : "=r" (cf) : "0" (ucf1.ll));
gcc/testsuite/gcc.c-torture/compile/pr55921.c:17:3: error: 'asm' operand has
impossible constraints
gcc/testsuite/gcc.c-torture/compile/pr55921.c:19:3: error: 'asm' operand has
impossible constraints
OK? This still triggers t
On Thu, 10 Jan 2013, Jakub Jelinek wrote:
> Hi!
>
> We weren't processing GIMPLE_ASMs that set complex SSA_NAMEs, which lead to
> SSA_NAMEs with NULL SSA_NAME_DEF_STMT, either leading to crashes or silent
> wrong code, depending on --enable-checking. Fixed thusly,
> bootstrapped/regtested on x86
Hi!
We weren't processing GIMPLE_ASMs that set complex SSA_NAMEs, which lead to
SSA_NAMEs with NULL SSA_NAME_DEF_STMT, either leading to crashes or silent
wrong code, depending on --enable-checking. Fixed thusly,
bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2013-01-09 Ja
