[klibc] Unsupported system calls
Anil Singhar
anil.singhar at linaro.org
Wed Oct 16 01:10:19 PDT 2013
OK, I will change all <!aarch64> to <?> then. How about lines declared like
the following:
<!alpha,aarch64,ia64,mips,mips64,sh,sparc,sparc64> int pipe(int *);
Should they also be changed to <?> ?
Thanks and Regards,
Anil
On 16 October 2013 13:32, H. Peter Anvin <hpa at zytor.com> wrote:
> On 10/16/2013 12:52 AM, Anil Singhar wrote:
> > Hi HPA,
> >
> > Thanks for your reply. One confusion I have is:
> >
> > e.g. 'access' is not supported in aarch64, so should the declaration be:
> >
> > <!aarch64> int access(const char *, int); <-- This is how it is
> currently
> > indicating that only aarch64 doesn't support it.
> >
> > OR
> >
> > <?> int access(const char *, int); <-- if I do this instead, it will be
> > optional for every architecture, right..?
> >
>
> Yes, and that is the right way to do it if there is a generic,
> non-architecture specific fallback in terms of another system call.
>
> -hpa
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.zytor.com/pipermail/klibc/attachments/20131016/8d430ff9/attachment.html>
More information about the klibc
mailing list