Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: Phasing out Dwarf 1?
Date: Wed, 05 May 2004 05:24:00 -0000	[thread overview]
Message-ID: <20040505052310.A2AF64B104@berman.michael-chastain.com> (raw)

Hi Andrew,

> I believe that you've already demonstrated that there are no dwarf-1 
> cross compilers left (they've all migrated to dwarf-2).

I'm a bit confused by the "cross compiler" part.  For gcc I looked at
the config/ bits for all the targets without regard to hosts, so I've
always been looking at both natives and crosses.  For diab and absoft I
read their online manuals and release notes.

> That just leaves us with dwarf-1 systems.  How many dwarf-1 systems does 
> GDB still support?  If we've also eliminated all our dwarf-1 systems, 
> there's little sense in retaining dwarf-1 support.

What do you mean by 'dwarf-1 system'?  If you include systems that
support both dwarf-1 and dwarf-2, even if dwarf-1 is not the default,
then up to gcc 3.3.3, that includes most ELF-based systems.  But all
those users have upgrade paths to dwarf-2.

If you mean, 'systems where prefer dwarf-1 is the preferred debugging
format', here's a table.

  gcc 3.4.0
    none

  gcc 3.3.2
    i[34567]86-sequent-ptx4*	no longer supported by gdb
    i[34567]86-sequent-sysv4*	no longer supported by gdb
    mips-sni-sysv4		no longer supported by gdb
    sparc-hal-solaris2*		still supported by gdb (i think)

  gcc 3.2.2
    all targets from gcc 3.3.3, plus
     i[34567]86-dg-dgux*	still supported by gdb
     m88k-dg-dgux*		no longer supported by gdb

  gcc 2.95.3
    all targets from gcc 3.2.2, plus
     i[34567]86-ncr-sysv4*	still supported by gdb
     i[34567]86-*-osf1*		no longer supported by gdb
     i[34567]86-*-sco3.2v5*	still supported by gdb
     i[34567]86-*-sysv4*	still supported by gdb
     i860-alliant-*		no longer supported by gdb
     i860-*-sysv4*		no longer supported by gdb
     m68k-atari-sysv4*		no longer supported by gdb
     m68k-cbm-sysv4*		no longer supported by gdb
     m68k-*-sysv4*		no longer supported by gdb
     m88k-*-sysv4*		no longer supported by gdb
     mips-*-gnu*		no longer supported by gdb
     sh-*-elf*			still supported by gdb
     sh-*-rtemself*		still supported by gdb
     sparc-*-sysv4*		still supported by gdb

That's just gcc.  It doesn't include systems with non-gcc compilers
that still emit dwarf-1.  I don't know if any such systems exist.

So if somebody has an i386-dg-dgux system, they could still be
using gcc 3.2.2 and dwarf-1.  Or i686-unknown-sco3.2v5 and
gcc 2.95.3.  Or sparc-*-sysv4* and gcc 2.95.3.

I'm not sure what the thrust of your question is so I don't know
if this is the info that you're looking for.

Michael C


             reply	other threads:[~2004-05-05  5:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  5:24 Michael Elizabeth Chastain [this message]
2004-05-05 14:31 ` Andrew Cagney
2004-05-05 16:05   ` Kean Johnston
2004-05-05 18:30     ` Stan Shebs
2004-05-05 18:53       ` Kean Johnston
  -- strict thread matches above, loose matches on Subject: below --
2004-05-06 15:00 Michael Elizabeth Chastain
2004-05-07  1:19 ` Andrew Cagney
2004-05-05 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
2004-05-05 21:33 Michael Elizabeth Chastain
2004-05-05  5:03 Michael Elizabeth Chastain
2004-05-03 15:56 Michael Elizabeth Chastain
2004-05-04 15:37 ` Andrew Cagney
2004-05-04 17:09   ` Nathan J. Williams
2004-05-04 17:19     ` Kean Johnston
2004-05-05  0:28       ` Stan Shebs
2004-05-05  5:57       ` Jim Blandy
2004-05-10 21:09     ` Andrew Cagney

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=20040505052310.A2AF64B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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