Re: input constraints in atomic.h too loose ?

On 2/2/07, Mike Frysinger <[email protected]> wrote:
> while building glibc-2.5/cvs with gcc-4.1.1, i hit an error about invalid
> operands in the locking code ... looks like the declared constraints for the
> inputs in atomic.h are too loose ?
>
> $ hppa2.0-unknown-linux-gnu-gcc -O1 -fPIC vfprintf.i -c

It is invalid to compiler glibc with less than -O2, you will not get a
build that works at -O1 because of the inlining requirements before
relocation.

> /tmp/ccvCRbqg.s: Assembler messages:
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: bad expression
> /tmp/ccvCRbqg.s:41: Error: Invalid operands
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: bad expression
> /tmp/ccvCRbqg.s:43: Error: Invalid operands

What *is* the bad assembly here. Please don't make me count assembly
line numbers, just point me at the bad asm.

Cheers,
Carlos.