This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: ARCv2 Public PRM (was Re: [PATCH v2 00/15] glibc port to ARC processors)
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Vineet Gupta <Vineet dot Gupta1 at synopsys dot com>
- Cc: "linux-snps-arc at lists dot infradead dot org" <linux-snps-arc at lists dot infradead dot org>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Thu, 6 Feb 2020 21:51:02 +0000
- Subject: Re: ARCv2 Public PRM (was Re: [PATCH v2 00/15] glibc port to ARC processors)
- Ironport-sdr: HKSfwJti4XV/4OHHnJ9H6KNcupUWIiTCDGCA3CIEpoeobaO2YfInvohy51+RqWgNjGujVHT9vO ktplJGHQlYMGmZcjSJggJfDRr5RX0C63Vs9e9hjxF1/SkpMC0WOwIur42y0N0YqyFsgmohhh8i uhlJCGE6gShVUPDzWVbZt6i+ayR1P/lWz8PoEBmPZ2q6FWvhXYy9WyUcFr17cOyeFtMJl+7JUr 1qbzfzWJqasx55qpF20FwCoUDjG8gApAU3MWeEsAQij/23Na81iV/fSHA0SUMN0WaJbc6qdiTT gt0=
- Ironport-sdr: ldNQ1LP1iD+idwrn4M7yyYKd8ImpuNB9dhmull8zOEb9P0CgrPiBTEKSEjNDD9+spgv9CJMqBq tLDF4hElLT8Mw5vaRUUdeFC/PHconUqq1m3lHQd4I8zS6IqoZ5K+mFNHc3F9GSt4p9YQsfaor3 ARWOnEb3RlTdfzgRSbasJ8vanGxI5ISdWjxbpnE82AatcKOthPUsL/RWpy5mTZqHfnRKt+/nnF d1e4DL+fIYOeCkVmtRaGXh/ucMXsmpkSwQkO3fFAH3NcqXxX19o2+7SyQhkgpadAaNK9b+Hu93 TFQ=
- References: <1548811555-24373-1-git-send-email-vgupta@synopsys.com> <alpine.DEB.2.21.1901300220520.24454@digraph.polyomino.org.uk> <980d8411-e4b9-24c0-3340-c112d6d6c349@synopsys.com> <c3e18811-b5ed-2194-ba55-6c5f87f46721@synopsys.com> <alpine.DEB.2.21.2001172136520.13033@digraph.polyomino.org.uk> <8311a699-183e-6811-cf24-3ad85ff80321@synopsys.com>
On Thu, 6 Feb 2020, Vineet Gupta wrote:
> > If
> > you require Linux 5.1 or later for the port then all or nearly all the
> > architecture-independent pieces required for a 32-bit port supporting only
> > 64-bit times should be covered by the RV32 patches, which I think are
> > quite close to being ready to go into glibc, though you'd need to watch
> > out for any (new or existing) #ifdef conditionals that might try to use
> > 32-bit-time syscalls if they exist (which they don't on RV32) - and that
> > would not prevent supporting older kernel versions later if desired, as
> > the Y2038 support gets built out (including, in particular, the support
> > for falling back to 32-bit-time syscalls in functions for 64-bit-time
> > interfaces).
>
> Ok I see patches in flight on the mailing list. Would it make sense for me to
> start off in parallel with ARC port which will take it's due course of review and
> rework and in that process upstream y2038 work settles down and I then
> rebase/switch ARC to that. Or would rather wait for upstream to settle down and
> then I adjust/post ?
I'd suggest posting patches that are on top of the RV32 ones (maybe
there's a git tree with RV32 changes to current glibc that could be used),
and that only support Linux 5.1 and later (so you don't need anything much
of the Y2038 support beyond what's in the RV32 patches).
--
Joseph S. Myers
joseph@codesourcery.com