From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>,
Aleksandar Ristovski <aristovski@qnx.com>
Subject: Re: [PATCH 1/3] gdb: remove native support for QNX Neutrino
Date: Wed, 9 Dec 2020 16:07:19 -0500 [thread overview]
Message-ID: <140514f9-0773-82d6-e905-03742ac29815@polymtl.ca> (raw)
In-Reply-To: <87zh2mr97l.fsf@tromey.com>
[Re-sending, I forgot to actually put Aleksandar in CC]
On 2020-12-09 3:54 p.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> Remove the native support for the QNX Neutrino OS. This has been
> Simon> unmaintained for years, and we don't even have a way to see if it builds
> Simon> or not. Without somebody actively maintaining it, this is just a burden
> Simon> for developers, having to do changes and guess if they'll even
> Simon> compile.
>
> I was curious when the last substantive patch was.
> I think it was 2015:
>
> commit a9889169e5b21efb8c42105fc62461be43968d64
> Author: Aleksandar Ristovski <aristovski@qnx.com>
> Date: Wed Oct 21 10:37:33 2015 -0400
>
> [nto] Fix nto target stopped by watchpoint.
>
> Aleksandar is still listed in MAINTAINERS, so maybe we ought to try to
> contact him before going forward?
Adding Aleksandar in CC.
Aleksandar, do you know if QNX is still interested in maintaining the Neutrino
support in upstream GDB? This is code that upstream maintainers can't test
(not even compile-test), so without involvement from QNX there's nothing we can
do to ensure the code still makes sense.
> MAINTAINERS has a lot of obsolete entries. So probably this doesn't
> mean much. Still, I guess it wouldn't hurt to wait a week or two,
> unless this is blocking some other work.
>
> To be clear, I'm in favor of removing things like this, particularly
> unmaintained targets and nat- code, as those are more difficult to test
> or even compile.
This is not urgent, so we can wait for a response from Aleksandar (hopefully).
Simon
prev parent reply other threads:[~2020-12-09 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 22:33 Simon Marchi via Gdb-patches
2020-12-07 22:33 ` [PATCH 2/3] gdbsupport: remove #ifndef REALTIME_LO in signals.cc Simon Marchi via Gdb-patches
2020-12-07 22:33 ` [PATCH 3/3] gdb: remove QNX Neutrino tdep support Simon Marchi via Gdb-patches
2020-12-08 15:04 ` Christian Biesinger via Gdb-patches
2020-12-08 15:30 ` Simon Marchi via Gdb-patches
2020-12-08 15:04 ` Eli Zaretskii via Gdb-patches
2020-12-08 15:06 ` [PATCH 1/3] gdb: remove native support for QNX Neutrino Eli Zaretskii via Gdb-patches
2020-12-08 15:10 ` Simon Marchi via Gdb-patches
2020-12-09 20:54 ` Tom Tromey
2020-12-09 21:06 ` Simon Marchi via Gdb-patches
2020-12-09 21:07 ` Simon Marchi via Gdb-patches [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=140514f9-0773-82d6-e905-03742ac29815@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=aristovski@qnx.com \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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