From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <palves@redhat.com>,
qiyaoltc@gmail.com, tom@tromey.com,
gdb-patches@sourceware.org
Subject: Re: [RFA 0/3] Fix various bugs found by static analysis
Date: Tue, 04 Oct 2016 20:43:00 -0000 [thread overview]
Message-ID: <87oa2z9771.fsf@tromey.com> (raw)
In-Reply-To: <8360p8lyui.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 04 Oct 2016 22:04:53 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> Shouldn't we wait for some time? I mean, gcj may have been removed,
Eli> but that doesn't mean all of its installations have been deleted, or
Eli> that no one out there uses the last release, and will use them for
Eli> some time.
Nobody has used it seriously in years. GCC dropping it is just the
final chapter, but really it died long ago. Fedora (not sure about
other distros) stopped shipping it a while ago and there's no critical
(or even useful) free software tool written using it. So, I think it's
safe to delete now. In the unlikely even that someone is using it, they
can debug with gdb 7.11.
Also, FWIW, it's not outrageously bad to debug gcj-compiled code as if
it were C++. You lose a little bit (String printing primarily) and you
have to use C++ names for things, but I think otherwise it works ok.
Tom
prev parent reply other threads:[~2016-10-04 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 21:54 Tom Tromey
2016-10-03 21:54 ` [RFA 3/3] PR remote/20655 - small fix in handle_tracepoint_bkpts Tom Tromey
2016-10-04 12:53 ` Yao Qi
2016-10-03 21:54 ` [RFA 2/3] PR gdb/20653 - small cleanup in string_to_explicit_location Tom Tromey
2016-10-03 22:27 ` Keith Seitz
2016-10-04 10:50 ` Yao Qi
2016-10-03 21:54 ` [RFA 1/3] PR symtab/20652 - fix psymbol_compare Tom Tromey
2016-10-04 10:55 ` Yao Qi
2016-10-04 18:37 ` Pedro Alves
2016-10-04 18:52 ` Tom Tromey
2016-10-04 15:14 ` [RFA 0/3] Fix various bugs found by static analysis Yao Qi
2016-10-04 18:31 ` Pedro Alves
2016-10-04 19:05 ` Eli Zaretskii
2016-10-04 20:43 ` Tom Tromey [this message]
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=87oa2z9771.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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