From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9731 invoked by alias); 6 Aug 2004 20:29:55 -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 9723 invoked from network); 6 Aug 2004 20:29:55 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 6 Aug 2004 20:29:55 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i76KTse3011257 for ; Fri, 6 Aug 2004 16:29:54 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i76KTra11292; Fri, 6 Aug 2004 16:29:54 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 254C02B9D; Fri, 6 Aug 2004 16:29:48 -0400 (EDT) Message-ID: <4113EA3B.3000900@gnu.org> Date: Fri, 06 Aug 2004 20:29:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Mark Kettenis Cc: eliz@gnu.org, gdb-patches@sources.redhat.com Subject: Re: [PATCH] Improve i386 prologue analyzer References: <200408012158.i71LwpRw033840@elgar.kettenis.dyndns.org> <3405-Mon02Aug2004070159+0300-eliz@gnu.org> <410EAFBB.5080102@gnu.org> <2914-Tue03Aug2004065313+0300-eliz@gnu.org> <200408061933.i76JX3HJ008032@elgar.kettenis.dyndns.org> In-Reply-To: <200408061933.i76JX3HJ008032@elgar.kettenis.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00171.txt.bz2 > Date: Tue, 03 Aug 2004 06:53:13 +0300 > From: "Eli Zaretskii" > > > Date: Mon, 02 Aug 2004 17:18:51 -0400 > > From: Andrew Cagney > > > > Should this be back-ported? > > Probably, especially if we are going to have GDB 6.2.1. This bug > means that anyone who uses GCC 3.3 and later will see bogus backtraces > in optimized programs. > > I was under the impression that it only affected GCC 3.4. Is GCC 3.3 > affected too Eli? > > I'd really like this to get some exposure in HEAD before backporting > it, but otherwise I do agree. Ah. We need to push the MIPS fixes out fairly quickly. Sounds like this should be held back, perhaphs for 6.3 or a 6.2.2. Andrew