From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: [cplus] An initial use of the canonicalizer
Date: Thu, 01 Jan 2004 07:50:00 -0000 [thread overview]
Message-ID: <20040101075036.GA1958@nevyn.them.org> (raw)
In-Reply-To: <ubrpo5ho8.fsf@elta.co.il>
On Thu, Jan 01, 2004 at 08:03:51AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 31 Dec 2003 14:04:10 -0500 (EST)
> > From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> >
> > Maybe stabs+ will go away by 2010.
>
> Not before DWARF2 becomes much more reliable than it is today, one
> would hope. Right now, at least in my experience, stabs+ is much
> more reliable than DWARF2.
I've found the exact opposite to be true. Sure, two years ago, the
story was different. But now GCC on our most-popular targets (GNU/Linux,
the BSDs) produces DWARF-2 by default and it works like a charm.
The space issue is still a big deal. We'll probably be hearing all
sorts of things about that, now, especially with Apple jumping on the
DWARF2 bandwagon for OS X. At least, tentatively.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-01 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 19:04 Michael Elizabeth Chastain
2004-01-01 6:03 ` Eli Zaretskii
2004-01-01 7:50 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 4:12 Michael Elizabeth Chastain
2003-12-31 14:04 ` Daniel Jacobowitz
2003-12-31 2:26 Michael Elizabeth Chastain
2003-12-31 3:36 ` Daniel Jacobowitz
2003-12-31 1:43 Michael Elizabeth Chastain
2003-12-31 2:09 ` Daniel Jacobowitz
2003-12-30 21:15 Michael Elizabeth Chastain
2003-12-31 0:59 ` Daniel Jacobowitz
2003-12-30 21:03 Daniel Jacobowitz
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=20040101075036.GA1958@nevyn.them.org \
--to=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--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