[COMMITTED] Move tilegx, tilepro, and linux-generic from ports to libc.
Commit Message
On 03/19/2015 01:18 PM, H.J. Lu wrote:
> Is the linux/generic scheme
> documented in glibc tree? Should there be a README in
> linux/generic directory?
It was not specifically documented, so I have added a README (and
committed it). I think it is probably worthwhile to see how much of the
existing linux/generic/wordsize-32 support can be used by x32 or
AArch64:ILP32. Some of it wouldn't apply (e.g. fstatfs.c, to take an
obvious example), but other parts might; I'm not sure. I guess the
kernel API is still being nailed down anyway.
Comments
On Thu, Mar 19, 2015 at 10:37 AM, Chris Metcalf <cmetcalf@ezchip.com> wrote:
> On 03/19/2015 01:18 PM, H.J. Lu wrote:
>>
>> Is the linux/generic scheme
>> documented in glibc tree? Should there be a README in
>> linux/generic directory?
>
>
> It was not specifically documented, so I have added a README (and committed
Thanks for doing it.
> it). I think it is probably worthwhile to see how much of the existing
> linux/generic/wordsize-32 support can be used by x32 or AArch64:ILP32. Some
Since x32 uses a combination of x86-64 and ia32 syscall interfaces,
x32 can't use linux/generic.
new file mode 100644
@@ -0,0 +1,11 @@
+This hierarchy supports Linux systems using the new
+asm-generic/unistd.h, which removes many familiar old syscalls. For
+example, to implement open(), newer Linux architectures require glibc
+to invoke the __NR_openat syscall with AT_FDCWD. This hierarchy
+provides all those implementations.
+
+It also provides support for 32-bit platforms using the 64-bit kernel
+syscall APIs, as the 32-bit ones are no longer provided. Note that
+newer ILP32 environments (x32 or AArch64:ILP32, for example) are
+converting to use more 64-bit types in kernel syscalls, so that aspect
+of this support is in more flux as of this writing.