Re: subtle bug in <include/asm-i386/unistd.h>

Markus F.X.J. Oberhumer (markus.oberhumer@jk.uni-linz.ac.at)
Wed, 31 Mar 1999 17:51:30 +0200 (CEST)


Yes, but please try the program I sent. This could also be
some gcc bug (happens with gcc 2.7.2 and egcs 1.1.1).

Markus

On 31-Mar-99 Andi Kleen wrote:
> markus.oberhumer@jk.uni-linz.ac.at (Markus F.X.J. Oberhumer) writes:
>>
>> --- include/asm/unistd.h.orig Tue Jan 26 16:00:03 1999
>> +++ include/asm/unistd.h Wed Mar 31 13:35:30 1999
>> @@ -214,7 +214,7 @@
>> long __res; \
>> __asm__ volatile ("int $0x80" \
>> : "=a" (__res) \
>> - : "0" (__NR_##name)); \
>> + : "a" (__NR_##name)); \
>> __syscall_return(type,__res); \
>> }
>
> ??? "0" means refer to operand 0, which is the "=a". Please see
> the gcc manual (C Extensions/Extended Asm) for read-write constraints.
> This is the prefered way to express them.
>
> -Andi
>
> --
> This is like TV. I don't like TV.
>

----- Markus Oberhumer <markus.oberhumer@jk.uni-linz.ac.at> -----
----- http://wildsau.idv.uni-linz.ac.at/mfx/ -----
----- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 -----

3 WARPS TO URANUS

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/