[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMe9rOrOR9yyYeWL07K0mwzEUD4Dd_2Ew4ntwqEZfS+4TJ5naw@mail.gmail.com>
Date: Wed, 11 Feb 2015 11:22:14 -0800
From: "H.J. Lu" <hjl.tools@...il.com>
To: musl@...ts.openwall.com, Rich Felker <dalias@...c.org>,
Andrew Pinski <apinski@...ium.com>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "pinskia@...il.com" <pinskia@...il.com>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>, Marcus Shawcroft <Marcus.Shawcroft@....com>
Subject: Re: Re: [PATCHv3 00/24] ILP32 support in ARM64
On Wed, Feb 11, 2015 at 11:05 AM, Szabolcs Nagy <nsz@...t70.net> wrote:
> i know at least one android kernel issue: there is an ioctl for the
> alarm device that takes timespec argument
>
> (i think it's not in the mainline kernel and i guess android does
> not care about x32 so it was not an issue so far, but this is something
> that should not be fixed on the libc side)
>
I have documented some remaining x32 kernel issues at:
https://sites.google.com/site/x32abi/
--
H.J.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
