From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tristan Gingold <gingold@adacore.com>,
"gdb-patches@sourceware.org ml"
<gdb-patches@sourceware.org>
Subject: Re: RFA: Try to include libunwind-ia64.h in libunwind-frame.h
Date: Tue, 21 Feb 2012 06:48:00 -0000 [thread overview]
Message-ID: <20120221052428.GA32408@host2.jankratochvil.net> (raw)
In-Reply-To: <4F42C295.6010905@redhat.com>
On Mon, 20 Feb 2012 23:00:53 +0100, Pedro Alves wrote:
> Fix GDB's broken inclusion of "libunwind.h".
> As I've explained before, including "libunwind.h" in GDB is _always_ wrong
> for GDB.
Not in the native mode. For example core files support on some platforms is
also supported only natively now.
> I don't imagine how any multi-arch work we do to libunwind would make it
> possible to include "libunwind.h".
For native build of GDB - which is IMO 99% of its builds - with a oneliner
patch of installing the unwinder it should work fully multi-arch.
After your patch it will be slightly more complicated patch to make the
libunwind support multi-arch (in native mode).
> But in any case, this is much more than the real need we have now. And I
> don't see why we can't fix the include problem, and do multi-arching as
> follow up work as necessary.
+
> I don't see how different the result will be from today's state,
Currently the code has some attempt to be multi-arch, despite not yet there.
Let's say it is in 50% of the multi-arch libunwind supports.
After this limitation to ia64 it will be at 30% of the multi-arch libunwind
support.
We have already spent more time talking about it than to either making it
ia64-exclusive making the support 0% or to making the support fully multi-arch
being 100% where nobody needs to talk about it anymore.
The code in GDB which no longer makes sense but still is neither removed nor
fixed makes it difficult for any contributions, coding, reviewing, anything,
besides a few people who know what it should mean one day in the future.
This is the reason why #if 0 code can be removed as [obv].
Thanks,
Jan
next prev parent reply other threads:[~2012-02-21 5:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 16:32 Tristan Gingold
2012-02-10 12:31 ` Jan Kratochvil
2012-02-10 13:15 ` Tristan Gingold
2012-02-10 13:21 ` Jan Kratochvil
2012-02-10 13:27 ` Joel Brobecker
2012-02-10 13:45 ` Tristan Gingold
2012-02-10 14:04 ` Tristan Gingold
2012-02-10 14:09 ` Jan Kratochvil
2012-02-10 14:14 ` Tristan Gingold
2012-02-10 18:27 ` Jan Kratochvil
2012-02-10 18:34 ` Pedro Alves
2012-02-10 18:44 ` Jan Kratochvil
2012-02-10 18:59 ` Pedro Alves
2012-02-10 19:38 ` Jan Kratochvil
2012-02-11 14:10 ` Jan Kratochvil
2012-02-13 8:41 ` Tristan Gingold
2012-02-13 18:58 ` Pedro Alves
2012-02-13 19:03 ` Jan Kratochvil
2012-02-13 19:20 ` Pedro Alves
2012-02-13 19:27 ` Jan Kratochvil
2012-02-13 20:05 ` Pedro Alves
2012-02-14 7:28 ` Jan Kratochvil
2012-02-14 12:14 ` Pedro Alves
2012-02-14 14:36 ` Jan Kratochvil
2012-02-14 14:53 ` Pedro Alves
2012-02-20 20:54 ` Jan Kratochvil
2012-02-20 22:30 ` Pedro Alves
2012-02-20 22:37 ` Joel Brobecker
2012-02-20 22:39 ` Joel Brobecker
2012-02-20 22:57 ` Pedro Alves
2012-02-20 23:20 ` Joel Brobecker
2012-02-21 6:48 ` Jan Kratochvil [this message]
2012-02-21 13:36 ` Pedro Alves
2012-02-21 19:10 ` Tom Tromey
2012-02-22 7:56 ` Tristan Gingold
2012-02-22 14:52 ` Jan Kratochvil
2012-02-21 20:18 ` Jan Kratochvil
2012-02-21 20:43 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120221052428.GA32408@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox