From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17006 invoked by alias); 23 May 2003 18:17:47 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 25254 invoked from network); 23 May 2003 18:06:14 -0000 Received: from unknown (HELO piper.synopsys.com) (204.176.21.196) by sources.redhat.com with SMTP; 23 May 2003 18:06:14 -0000 Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id h4NI5XM26471; Fri, 23 May 2003 11:05:33 -0700 Date: Fri, 23 May 2003 18:17:00 -0000 From: Joe Buck To: Peter Barada Cc: ghazi@caip.rutgers.edu, dj@redhat.com, crossgcc@sources.redhat.com, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, peter@baradas.org Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?) Message-ID: <20030523110533.A26456@synopsys.com> References: <20030520053204.ADDB298982@baradas.org> <200305201609.h4KG9jR20778@greed.delorie.com> <200305202059.QAA18111@caip.rutgers.edu> <200305202138.h4KLccd26075@greed.delorie.com> <200305231529.LAA21736@caip.rutgers.edu> <20030523104125.B25849@synopsys.com> <200305231758.h4NHwAu06767@hyper.wm.sps.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200305231758.h4NHwAu06767@hyper.wm.sps.mot.com>; from pbarada@mail.wm.sps.mot.com on Fri, May 23, 2003 at 01:58:10PM -0400 X-SW-Source: 2003-05/txt/msg02115.txt.bz2 On Fri, May 23, 2003 at 01:58:10PM -0400, Peter Barada wrote: > >Ideally there should be a PR for this problem, so I can point to it in > >the 3.3.1 release notes. Any volunteers to make one? I would, but I > >don't know what platforms that this problem causes a failure for. > > I found it for --target=m68k-elf, but I think it shows up for other targets. > > See: > http://gcc.gnu.org/ml/gcc/2003-05/msg01836.html > http://gcc.gnu.org/ml/gcc/2003-05/msg01840.html > http://gcc.gnu.org/ml/gcc/2003-05/msg01904.html Would you mind writing it up as a PR? It would suffice to report it just against m68-elf, mentioning any other target that you know about.