From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22103 invoked by alias); 12 Nov 2011 02:43:03 -0000 Received: (qmail 22087 invoked by uid 22791); 12 Nov 2011 02:43:03 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Nov 2011 02:42:48 +0000 Received: from klappe2.localnet (24-196-174-139.dhcp.ahvl.nc.charter.com [24.196.174.139]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MYtGN-1RTgGv0CDT-00Vrzv; Sat, 12 Nov 2011 03:42:34 +0100 From: Arnd Bergmann To: Roland McGrath Subject: Re: [PATCH v2 0/10] Tilera (and Linux asm-generic) support for glibc Date: Sat, 12 Nov 2011 02:43:00 -0000 User-Agent: KMail/1.12.2 (Linux/3.2.0-rc1+; KDE/4.3.2; x86_64; ; ) Cc: Chris Metcalf , Ulrich Drepper , libc-alpha@sourceware.org, libc-ports@sourceware.org, Linas Vepstas , Guan Xuetao , Jonas Bonn , Chen Liqin References: <201111100054.pAA0sf6u025585@farm-0002.internal.tilera.com> <4EBD94B4.4050009@tilera.com> <20111111214214.BC66D2C0FE@topped-with-meat.com> In-Reply-To: <20111111214214.BC66D2C0FE@topped-with-meat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111120242.29691.arnd@arndb.de> Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00038.txt.bz2 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? Arnd