From: Mark Kettenis <kettenis@chello.nl>
To: mec.gnu@mindspring.com
Cc: cagney@gnu.org, jkj@sco.com, ezannoni@redhat.com,
gdb@sources.redhat.com, jimb@redhat.com,
mec.dot.gnu.at.mindspring.dot.com@elgar.kettenis.dyndns.org
Subject: Re: Phasing out Dwarf 1?
Date: Thu, 06 May 2004 20:11:00 -0000 [thread overview]
Message-ID: <200405062008.i46K8al6001432@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040505220132.260584B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
Date: Wed, 5 May 2004 18:01:32 -0400 (EDT)
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Solaris X86:
Mark, can you say anything about this? What debug format does "cc -g"
produce on a solaris x86 machine?
Not really. The OS doesn't come with a bundled compiler. So I only
use GCC. Sun's unbundled compiler on SPARC uses stabs by default,
although there is an option to generate dwarf. I don't know whether
that's DWARF 1 or 2. There seems to be some evidence that it's DWARF
2. I think dropping support for DWARF 1 is acceptable for
i[3-7]86-*-solaris2*.
Mark
next prev parent reply other threads:[~2004-05-06 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis [this message]
-- 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 21:33 Michael Elizabeth Chastain
2004-05-05 5:24 Michael Elizabeth Chastain
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
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=200405062008.i46K8al6001432@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jkj@sco.com \
--cc=mec.dot.gnu.at.mindspring.dot.com@elgar.kettenis.dyndns.org \
--cc=mec.gnu@mindspring.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