From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27642 invoked by alias); 5 Jul 2009 21:12:02 -0000 Received: (qmail 27634 invoked by uid 22791); 5 Jul 2009 21:12:02 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Jul 2009 21:11:54 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DE03710966; Sun, 5 Jul 2009 21:11:51 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id B6305108A5; Sun, 5 Jul 2009 21:11:51 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MNZ02-0000A5-ID; Sun, 05 Jul 2009 17:11:50 -0400 Date: Sun, 05 Jul 2009 21:12:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Mark Kettenis , gdb-patches@sourceware.org, teawater@gmail.com Subject: Re: [RFA] epilogue unwinder for i386 (reverse 1/2) Message-ID: <20090705211150.GA32102@caradoc.them.org> Mail-Followup-To: Michael Snyder , Mark Kettenis , gdb-patches@sourceware.org, teawater@gmail.com References: <4A4EA0F7.1040004@vmware.com> <4A4EA3B3.9030107@vmware.com> <200907051235.n65CZhDb024857@brahms.sibelius.xs4all.nl> <20090705184849.GA15042@caradoc.them.org> <4A51105D.5010400@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A51105D.5010400@vmware.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00117.txt.bz2 On Sun, Jul 05, 2009 at 01:43:09PM -0700, Michael Snyder wrote: > I would like that too -- maybe you can point me at an example? > > I'm thinking that even if GCC 4.5 fixes the issue, people will > continue to use older GCCs for a while. Sorry, unfinished thought on my part - I meant to say that someday, I'd like to add a way to detect the fixed GCC and disable this. There isn't a similar example yet. -- Daniel Jacobowitz CodeSourcery