This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2 0/10] Tilera (and Linux asm-generic) support for glibc
- From: Arnd Bergmann <arnd at arndb dot de>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: Chris Metcalf <cmetcalf at tilera dot com>,Ulrich Drepper <drepper at gmail dot com>,libc-alpha at sourceware dot org,libc-ports at sourceware dot org,Linas Vepstas <linas at codeaurora dot org>,Guan Xuetao <gxt at mprc dot pku dot edu dot cn>,Jonas Bonn <jonas at southpole dot se>,Chen Liqin <liqin dot chen at gmail dot com>
- Date: Sat, 12 Nov 2011 02:42:29 +0000
- Subject: Re: [PATCH v2 0/10] Tilera (and Linux asm-generic) support for glibc
- References: <201111100054.pAA0sf6u025585@farm-0002.internal.tilera.com> <4EBD94B4.firstname.lastname@example.org> <20111111214214.BC66D2C0FE@topped-with-meat.com>
On Friday 11 November 2011, Roland McGrath wrote:
> > For what it's worth, I know that there are other architectures waiting
> > to benefit from glibc support for the new Linux "asm-generic" ABI, so
> > there is certainly interest in the community.
> That's all still libc-ports territory.
Is this going to change with ARMv8? Right now, we only have openrisc, unicore32,
hexagon, c6x, and tile using the common ABI, plus lm32, nios2, unicore64 and a
few even lesser ones lined up, all of which are certainly libc-ports material.
However, 64 bit armv8 is looking like it will have broad support from
hardware and linux vendors, certainly more so than ia64, sh or sparc, which
are all currently part of the main glibc repository. Is the policy to simply
maintain the status quo or would armv8 get put into the main glibc tree once
it reaches critical mass?