From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 314 invoked by alias); 15 Jun 2012 16:41:50 -0000 Received: (qmail 305 invoked by uid 22791); 15 Jun 2012 16:41:49 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 Jun 2012 16:41:37 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1SfZaZ-0000Dx-GR from joseph_myers@mentor.com ; Fri, 15 Jun 2012 09:41:35 -0700 Received: from digraph.polyomino.org.uk ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 15 Jun 2012 17:41:33 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.74) (envelope-from ) id 1SfZaW-0003Jo-M1; Fri, 15 Jun 2012 16:41:32 +0000 Date: Fri, 15 Jun 2012 16:41:00 -0000 From: "Joseph S. Myers" To: Mark Salter cc: libc-ports@sourceware.org, Mike Frysinger , Andreas Schwab , Richard Henderson , Carlos O'Donell Subject: Re: Ports state for 2.16 regarding global changes In-Reply-To: <1339777097.32384.35.camel@deneb.redhat.com> Message-ID: References: <1339777097.32384.35.camel@deneb.redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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-06/txt/msg00050.txt.bz2 On Fri, 15 Jun 2012, Mark Salter wrote: > On Fri, 2012-06-15 at 15:52 +0000, Joseph S. Myers wrote: > > * am33: generally massively out of date and I have not tried to > > identify specific changes needed. > > I have been working on getting this updated. ATM, I'm blocked waiting on > a fix for a bug in the gcc patch adding am33 tls support. I expect to be > past this sometime next week so I can actually start testing things. > > Would it be helpful to go ahead and post the glibc patches now or wait > until I get them tested? I think it makes sense to post them now. I guess you'll have a small patch to libc - adding new relocations to elf.h - which should be sent to libc-alpha and should be safe even during the freeze, and the rest should be for ports. If the patches pass review then I think we should give you write access and make you am33 maintainer so you can apply further am33 patches without prior review - given the present state of am33 support (i.e. not substantively maintained since 2004), the changes are hardly going to make things any worse. (Updates to libc's README and NEWS files of course wait until the port is actually working.) -- Joseph S. Myers joseph@codesourcery.com