From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17686 invoked by alias); 28 Jan 2013 21:08:58 -0000 Received: (qmail 17636 invoked by uid 22791); 28 Jan 2013 21:08:57 -0000 X-SWARE-Spam-Status: No, hits=-4.5 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; Mon, 28 Jan 2013 21:08:52 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1Tzvwi-0003QQ-9n from Maciej_Rozycki@mentor.com ; Mon, 28 Jan 2013 13:08:52 -0800 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Jan 2013 13:08:51 -0800 Received: from [172.30.6.221] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.1.289.1; Mon, 28 Jan 2013 21:08:49 +0000 Date: Mon, 28 Jan 2013 21:08:00 -0000 From: "Maciej W. Rozycki" To: Steve Ellcey CC: "libc-alpha@sourceware.org" , "libc-ports@sourceware.org" , Chung-Lin Tang Subject: RE: [PATCH 2/2] MIPS16: MIPS16 support proper In-Reply-To: <1359395762.32571.15.camel@ubuntu-sellcey> Message-ID: References: <1359151771.11963.200.camel@ubuntu-sellcey> <1359394555.32571.12.camel@ubuntu-sellcey> <1359395762.32571.15.camel@ubuntu-sellcey> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) 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: 2013-01/txt/msg00069.txt.bz2 On Mon, 28 Jan 2013, Steve Ellcey wrote: > Following up to my own email, I think I was wrong about codesourcery > using mips32 code in .init/.fini, it looks like they have a GCC patch > to define CRT_CALL_STATIC_FUNCTION differently for mips16/mips32. I am > going to try and apply that patch to my ToT GCC and see what happens. Indeed, I wasn't aware there was an outstanding change there. Sorry about that. I think for now our best option is to follow Richard's suggestion. I'll take it into account with the upcoming patch update. Maciej