Re: syscall macro fails upon compilation

[H. Peter Anvin]

Andi Kleen wrote:
> "H. Peter Anvin" <hpa@xxxxxxxxx> writes:
> 
>> Gautam Singaraju wrote:
>>> I use the _syscall0 macro.
>> Don't.  The _syscall*() macros have been unsupported for ages,
> 
> That's not true. I supported them on x86 before they were removed against
> my objections.
> 
>> and broken for ever longer.
> 
> Well, most syscall() versions get 6 argument calls wrong
> (not sure if that is finally fixed). _syscall*() didn't support
> -fPIC for larger argument counts (_syscall0-2 never had a problem) 
> 
> So all alternatives short of writing your own stub had various
> issues. If you needed 6 argument calls _syscall* was typically
> the best alternative.
> 

They were *always* broken for 64-bit arguments on 32-bit machines, however.

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