From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23726 invoked by alias); 21 Feb 2012 17:24:29 -0000 Received: (qmail 23708 invoked by uid 22791); 21 Feb 2012 17:24:27 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from anubis.se.axis.com (HELO anubis.se.axis.com) (195.60.68.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 21 Feb 2012 17:23:46 +0000 Received: from localhost (localhost [127.0.0.1]) by anubis.se.axis.com (Postfix) with ESMTP id E2A3619E6E; Tue, 21 Feb 2012 18:23:44 +0100 (CET) Received: from anubis.se.axis.com ([127.0.0.1]) by localhost (anubis.se.axis.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7W9K5spfjngk; Tue, 21 Feb 2012 18:23:39 +0100 (CET) Received: from seth.se.axis.com (seth.se.axis.com [10.0.2.172]) by anubis.se.axis.com (Postfix) with ESMTP id 5F5AC19DD5; Tue, 21 Feb 2012 18:23:39 +0100 (CET) Received: from ignucius.se.axis.com (ignucius.se.axis.com [10.88.21.50]) by seth.se.axis.com (Postfix) with ESMTP id 00E093E09A; Tue, 21 Feb 2012 18:23:39 +0100 (CET) Received: from ignucius.se.axis.com (localhost [127.0.0.1]) by ignucius.se.axis.com (8.12.8p1/8.12.8/Debian-2woody1) with ESMTP id q1LHNcF6006507; Tue, 21 Feb 2012 18:23:38 +0100 Received: (from hp@localhost) by ignucius.se.axis.com (8.12.8p1/8.12.8/Debian-2woody1) id q1LHNckx006503; Tue, 21 Feb 2012 18:23:38 +0100 Date: Tue, 21 Feb 2012 17:24:00 -0000 Message-Id: <201202211723.q1LHNckx006503@ignucius.se.axis.com> From: Hans-Peter Nilsson To: joseph@codesourcery.com CC: libc-ports@sourceware.org, aoliva@redhat.com In-reply-to: (joseph@codesourcery.com) Subject: Re: glibc am33 and cris architectures MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT 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: 2012-02/txt/msg00070.txt.bz2 > From: "Joseph S. Myers" > Date: Tue, 21 Feb 2012 16:21:12 +0100 > The am33 and cris glibc ports won't have worked since the 2.3-2.5 era for > lack of NPTL/TLS support. They are currently on the deprecation list for > removal after glibc 2.16 is released > . But given how long they > won't have worked, I wonder if we should just remove them now. For CRIS, I'd suggest to do that. > Alexandre, > Hans-Peter - do you have, or know of, any near-term plans to bring your > respective ports up to date with NPTL and TLS support and updates for all > the other libc changes in the past several years? JFTR, there's a local port, specific to CRIS v32 (a later variant), with the glibc part based on an import of the eglibc-2.9 branch. Linux TLS support (yes, I do mean just the kernel) is currently missing for CRIS. That is, it's missing for CRIS v10, the original GNU/Linux-capable variant (disregarding earlier MMU-less variants): anyone interested is advised to please use either $IRP or $BRP as the thread-pointer register; use the CRIS v32 Linux support as a template with minor changes in thread-pointer-setting and most changes for restoring that register at return from interrupt or breakpoint or syscall return. GCC TLS support for CRIS v32 needs to be updated and committed anyway, by itself the least complex part, but not trivial and even that part is not imminent though hopefully will happen in the first half of this year. Still, no commitment for any work in a time-frame I'd dare call near-term. Thus, just a glibc CRIS port update right now wouldn't do much good in practice. When doing the (e)glibc import part of the TLS support, I noticed how much had changed since last synch. I suggest that even if someone else were to do independent work, it'd be better to start from scratch than be distracted by the half-way-commit of the originally submitted code that's currently in place. Best to remove it; it'll just bloat any CRIS-related patches. brgds, H-P (PS. but at least the binutils TLS part is all committed. :)