[PATCH] [BZ #19371] Properly handle x32 syscall

[H.J. Lu]

On Wed, Dec 16, 2015 at 4:53 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Wed, 16 Dec 2015, H.J. Lu wrote:
>
>> > Sorry, I was talking about manual/startup.texi:
>> >
>> > manual/startup.texi:727:@deftypefun {long int} syscall (long int
>> > @var{sysno}, @dots{})
>> > manual/startup.texi-728-@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
>> > manual/startup.texi-729-
>> > manual/startup.texi-730-@code{syscall} performs a generic system call.
>> >
>>
>> Here is the updated patch.  OK for master?
>
> That can't possibly be right.  User documentation needs to be in terms of
> types exposed to the user (and documented as such), not anything starting
> __.

It is lower priority for me since people should use lseek, time and
times instead of syscall ().


-- 
H.J.