Messages in this thread | | | Subject | Re: subtle bug in <include/asm-i386/unistd.h> | From | Andi Kleen <> | Date | 31 Mar 1999 17:29:18 +0200 |
| |
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.
- 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/
| |