From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32433 invoked by alias); 26 Nov 2013 18:54:23 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 32423 invoked by uid 89); 26 Nov 2013 18:54:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: eggs.gnu.org Received: from Unknown (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 26 Nov 2013 18:54:21 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlNlx-0006r7-Dv for gcc@gcc.gnu.org; Tue, 26 Nov 2013 13:54:13 -0500 Received: from oarmail.oarcorp.com ([67.63.146.244]:32246) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlNlw-0006qv-Sa for gcc@gcc.gnu.org; Tue, 26 Nov 2013 13:54:09 -0500 Received: from [192.168.1.162] (192.168.1.162) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Nov 2013 12:52:25 -0600 Message-ID: <5294EE43.5000000@oarcorp.com> Date: Tue, 26 Nov 2013 18:54:00 -0000 From: Joel Sherrill User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Ralf Corsepius , "gcc@gcc.gnu.org" Subject: Re: [buildrobot] microblaze-elf / microblaze-linux References: <1djbjk1n62mkaiqxbjm4lo51.1385469317186@email.android.com> <20131126145119.GQ30563@lug-owl.de> <20131126152755.GR30563@lug-owl.de> <5294DC85.4030700@oarcorp.com> <5294E12B.7080908@rtems.org> In-Reply-To: <5294E12B.7080908@rtems.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Windows XP X-Received-From: 67.63.146.244 X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00549.txt.bz2 On 11/26/2013 11:58 AM, Ralf Corsepius wrote: > On 11/26/2013 06:38 PM, Joel Sherrill wrote: > >>> Is there something that microblaze-rtems exposes that is not already >>> covered by other microblaze or rtems targets that are already included? >> >> I believe it was on the microblaze where someone broke the >> libgcc pattern for rtems by changing the pattern from >> XXX*-*-* to XXX*-*-elf. > Correct. microblaze-rtems* is incomplete in libgcc. > > I have a patch pending for gcc-4.8.x, but haven't yet tried with > gcc-4.9.x. It should be the same patch. I wrote one too and obviously forgot to upstream it. For those who care, this is the seemingly benign patch which broke it. http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=98f2ac05e3adaf283a55531a3e274e20aad6048d The lesson is that every target has to take a path through those large switches. And things can and do break. > Ralf > > -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherrill@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985