From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10908 invoked by alias); 2 May 2005 15:58:03 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10826 invoked from network); 2 May 2005 15:57:54 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 2 May 2005 15:57:54 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j42Fvswv015917 for ; Mon, 2 May 2005 11:57:54 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j42FvnO04209; Mon, 2 May 2005 11:57:49 -0400 Received: from [172.16.50.56] (vpn50-56.rdu.redhat.com [172.16.50.56]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j42Fvl1K030889; Mon, 2 May 2005 11:57:47 -0400 Message-ID: <42764DD6.3070902@gnu.org> Date: Mon, 02 May 2005 15:58:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 1.0.2-1 (X11/20050323) MIME-Version: 1.0 To: Mark Kettenis CC: gdb-patches@sources.redhat.com Subject: Re: [commit] note non-building architectures References: <42756233.5080809@gnu.org> <200505012332.j41NWMH0026515@elgar.sibelius.xs4all.nl> In-Reply-To: <200505012332.j41NWMH0026515@elgar.sibelius.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00050.txt.bz2 Mark Kettenis wrote: > Date: Sun, 01 May 2005 19:11:47 -0400 > From: Andrew Cagney > > As part of getting ready for GCC 4, I've found that a number of arches > don't build with gcc-3.4 when using gdb_mbuild.sh. As an aid, and to > stop me and presumably others from going round in circles, I've updated > the MAINTAINERS file to both reflect current reality note the problem. > > I think your GCC 3.4 is busted. My GCC? What a strange turn of expression. I'm pretty sure the warning will also happen with your gcc. Anyway, given that these problems are occuring in binutils directories and hence cause binutils builds to also fail, and the thing to do is persue the problem there. Andrew > I must admit that I don't really > understand that longjmp clobber warning message is warning about > exactly, but returning -1 immediately after a setjmp() call when that > has been jumped to, seems entirely safe to me. > > - m68k --target=m68k-elf ,-Werror > + m68k --target=m68k-elf broken > + (opcodes/m68k-dis.c:338 longjmp clober) > > - vax --target=vax-netbsd ,-Werror > + vax --target=vax-netbsd broken > + (opcodes/vax-dis.c:224 longjmp clober) > > Mark >