From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for -gstabs+ [Re: FYI: fix spelling of "delete" in c-exp.y]
Date: Tue, 19 Jun 2012 15:05:00 -0000 [thread overview]
Message-ID: <20120619150428.GA5427@host2.jankratochvil.net> (raw)
In-Reply-To: <877gv3pf4g.fsf@fleche.redhat.com>
On Tue, 19 Jun 2012 16:09:51 +0200, Tom Tromey wrote:
> Why are we spending any time at all on stabs and C++? IIRC that never
> really worked that well, and stabs are past obsolete.
If we understand why is it as it is (currently I do not) I have no problem
with anything about stabs. -gstabs+ already had/has many other C++ failures.
I will also look at it more.
Thanks,
Jan
next prev parent reply other threads:[~2012-06-19 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 20:22 FYI: fix spelling of "delete" in c-exp.y Tom Tromey
2012-06-19 10:49 ` Regression for -gstabs+ [Re: FYI: fix spelling of "delete" in c-exp.y] Jan Kratochvil
2012-06-19 14:10 ` Tom Tromey
2012-06-19 15:05 ` Jan Kratochvil [this message]
2012-06-19 17:24 ` Tom Tromey
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=20120619150428.GA5427@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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