From: Daniel Jacobowitz <drow@mvista.com>
To: Geoff Keating <geoffk@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Change rs6000 ELF targets to use DWARF2 by default in GCC.
Date: Sun, 12 Aug 2001 23:49:00 -0000 [thread overview]
Message-ID: <20010812234909.A15832@nevyn.them.org> (raw)
In-Reply-To: <200108130651.XAA07256@geoffk.org>
On Sun, Aug 12, 2001 at 11:51:57PM -0700, Geoff Keating wrote:
>
> I understand that while DWARF2 may be bigger, it is also more
> complete, and in particular it has a better chance of dealing with the
> new optimisations. I would rather better debugging information than
> smaller debugging information, and those who disagree can always use
> -g1 (or -gstabs for that matter).
>
> Tested on powerpc-eabisim. I didn't test gdb as I can't tell which
> failures would be "normal" for dwarf2. I am nonetheless hoping
> that gdb's testresults on powerpc will improve because of this patch.
>
> I've actually had this patch in my local tree for about 4 months, but
> it's only recently that the automated tester has managed to upgrade
> its binutils; there is an essential binutils patch that's required for
> GCC's libraries to build on the EABI targets (to support
> -mrelocatable).
What do you think of doing a similar thing to all the non-rs6000 Linux
targets in addition, and possibly any others that it seems to be safe
on - all on a case by case basis with GDB testsuites, where possible?
I know that at least SH-Linux (and ia64? I believe) already use DWARF2
by default. I believe there's a binutils problem preventing me from
using DWARF2 on MIPS, but it may have been fixed recently...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-08-12 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 23:34 Geoff Keating
2001-08-12 23:49 ` Daniel Jacobowitz [this message]
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=20010812234909.A15832@nevyn.them.org \
--to=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=geoffk@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