From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1067 invoked by alias); 13 Feb 2012 19:03:17 -0000 Received: (qmail 1055 invoked by uid 22791); 13 Feb 2012 19:03:16 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Mon, 13 Feb 2012 19:02:50 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q1DJ2SLc004028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Feb 2012 14:02:28 -0500 Received: from host2.jankratochvil.net (ovpn-116-26.ams2.redhat.com [10.36.116.26]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q1DJ2OjS027483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 14:02:26 -0500 Date: Mon, 13 Feb 2012 19:03:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: Tristan Gingold , "gdb-patches@sourceware.org ml" Subject: Re: RFA: Try to include libunwind-ia64.h in libunwind-frame.h Message-ID: <20120213190223.GA8851@host2.jankratochvil.net> References: <5D1CD28F-F628-475C-B6D8-5FCBF5290C63@adacore.com> <20120210182705.GA32459@host2.jankratochvil.net> <4F3562FE.7050106@redhat.com> <20120211140919.GA24043@host2.jankratochvil.net> <4F395D17.5070303@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F395D17.5070303@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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: 2012-02/txt/msg00242.txt.bz2 On Mon, 13 Feb 2012 19:57:27 +0100, Pedro Alves wrote: > I don't understand why we ever include "libunwind.h" though. > libunwind is only ever used by ia64 currently. It is required for ia64 but it can be used even with non-ia64 archs. I do not have it tested, though. I will test it before a check-in. > If some other target wanting to use libunwind shows up, then we'll need to > include libunwind-fooarch.h instead For native configuration libunwind.h includes the right libunwind-fooarch.h for us. /usr/include/libunwind.h #if defined __arm__ # include "libunwind-arm.h" #elif defined __hppa__ # include "libunwind-hppa.h" [...] The cross-build does not work for ia64 well this way, though. So libunwind for non-ia64 works even in the non-cross mode. This is the part I did not want to start implementing as it may get all more complex. > IOW, "libunwind.h" will always be conceptually wrong for gdb. libunwind has pretty active development, I can imaging libunwind developers / enthusiasts would like to use it for GDB on x86*. Thanks, Jan