public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: Deprecate dwarf and mdebug support, delete nlm?
Date: Sun, 04 May 2003 06:10:00 -0000	[thread overview]
Message-ID: <200305040610.h446Aa9D005783@duracef.shout.net> (raw)

I've been waiting for DWARF 1 to come up.  Here are some random facts:

I've run the test suite with -gdwarf and -gdwarf+.  My results were
40+ ERRORs and 3400+ FAILs.

In gcc 3.2.2, these targets prefer DWARF 1:

  i[34567]86-dg-dgux*
  i[34567]86-sequent-ptx4*
  i[34567]86-sequent-sysv4*
  m88k-dg-dgux*
  mips-sni-sysv4
  sparc-hal-solaris2*

I also have a list for gcc 2.95.3, which is quite a bit longer.

  i[34567]86-dg-dgux*
  i[34567]86-ncr-sysv4*
  i[34567]86-sequent-ptx4*
  i[34567]86-sequent-sysv4*
  i[34567]86-*-osf1*
  i[34567]86-*-sco3.2v5*
  i[34567]86-*-sysv4*
  i860-alliant-*
  i860-*-sysv4*
  m68k-atari-sysv4*
  m68k-cbm-sysv4*
  m68k-*-sysv4*
  m88k-dg-dgux*
  m88k-*-sysv4*
  mips-sni-sysv4
  mips-*-gnu*
  sh-*-elf*
  sh-*-rtemself*
  sparc-hal-solaris2*
  sparc-*-sysv4*

The real hang-up is non-gcc compilers that emit DWARF 1.

I recall seeing two instances of that in bug reports in the past year, 
but I don't have URL's handy.

Michael C

             reply	other threads:[~2003-05-04  6:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04  6:10 Michael Elizabeth Chastain [this message]
2003-05-04  6:43 ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:47 Michael Elizabeth Chastain
2003-05-09 16:37 ` Kean Johnston
2003-05-09 17:03   ` Andrew Cagney
2003-05-09 16:48 ` Andrew Cagney
2003-05-10  9:25   ` Eli Zaretskii
2003-05-09 15:22 Michael Elizabeth Chastain
2003-05-09 15:34 ` Kean Johnston
2003-05-09  8:10 Armin Diehl
     [not found] <200305082242.h48MgQH06975@mx1.redhat.com>
2003-05-09  0:02 ` Elena Zannoni
     [not found] <E19Duaa-0005kw-00@monty-python.gnu.org>
2003-05-08 23:42 ` Andrew Cagney
2003-05-09 15:12   ` Kean Johnston
2003-05-08 23:14 Günter Knauf
2003-05-08 22:52 Ulrich Neumann
2003-05-09  0:09 ` Elena Zannoni
2003-05-08 22:42 Günter Knauf
2003-05-04 16:08 Michael Elizabeth Chastain
2003-05-05 15:23 ` Tim Combs
2003-05-05 17:30   ` Andrew Cagney
2003-05-05 17:49     ` Daniel Berlin
2003-05-04  4:41 Andrew Cagney
2003-05-04 15:41 ` Daniel Jacobowitz
2003-05-04 19:52 ` Elena Zannoni
2003-05-05 17:37   ` Andrew Cagney
2003-05-05  0:14 ` Andrew Cagney
2003-05-05  3:58 ` Joel Brobecker
2003-05-05 17:24 ` Jim Blandy

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=200305040610.h446Aa9D005783@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).