From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7504 invoked by alias); 15 Oct 2009 18:00:46 -0000 Received: (qmail 7489 invoked by uid 22791); 15 Oct 2009 18:00:44 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Oct 2009 18:00:40 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9FI0FOo018023; Thu, 15 Oct 2009 14:00:15 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n9FI0EE9020356; Thu, 15 Oct 2009 14:00:15 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n9FI0Do0017611; Thu, 15 Oct 2009 14:00:14 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 59F2137828F; Thu, 15 Oct 2009 12:00:13 -0600 (MDT) From: Tom Tromey To: Joel Brobecker Cc: Michael Eager , "gdb-patches\@sourceware.org" Subject: Re: [PATCH] Support for Xilinx MicroBlaze References: <4AD74E86.1020500@eagercon.com> <20091015164724.GC5272@adacore.com> Reply-To: Tom Tromey Date: Thu, 15 Oct 2009 18:00:00 -0000 In-Reply-To: <20091015164724.GC5272@adacore.com> (Joel Brobecker's message of "Thu, 15 Oct 2009 09:47:25 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-10/txt/msg00348.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: Tom> How would this be done? Tom> Users might be using an old gcc or a new one. Joel> The only solution I see to this problem would be that users of a recent Joel> GCC would have to use a recent GDB. The problem is that this also implies that users stuck on an old compiler will be stuck with an old gdb. Joel> Worse case scenario, a microblase-specific setting. Yeah. Or parsing the dwarf producer string. Tom