From: Simon Marchi <simon.marchi@polymtl.ca>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH] Fix usage of inferior_ptid in two thread_alive implementations
Date: Thu, 30 Mar 2017 00:51:00 -0000 [thread overview]
Message-ID: <a6083dbb240011fe3de9834d0388bf66@polymtl.ca> (raw)
In-Reply-To: <2339561.2zYrb3lbLI@ralph.baldwin.cx>
On 2017-03-29 15:32, John Baldwin wrote:
> I don't think any modern versions of either FreeBSD or OpenBSD
> use bsd-uthread.c. The uthread target is for a thread implementation
> that only provided threads in userland on top of a single process
> (like "green" threads in the JDK). FreeBSD last shipped a release
> with support for this thread model (FreeBSD 6.4) in 2008. I can't
> speak to when OpenBSD stopped using user-based threads, but the
> existence of kernel-based thread support in the obsd-nat target
> implies it isn't used anymore either. For FreeBSD at least I think
> it would be fine to remove bsd-uthread.c.
>
> (I should also send a patch in to remove FreeBSD/alpha as that
> platform was retired at around the same time. The last release
> to support alpha was 6.3 also released in 2008.)
Thanks for the reply, this is very valuable information.
I would appreciate very much any effort to remove obsolete targets, as
it has some maintenance cost. For example, doing refactors that require
touching all the targets (such as changing the interface of a target_ops
method) is very long. If we can remove any target that has no reason to
be today, it can only help.
Simon
prev parent reply other threads:[~2017-03-30 0:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 21:25 Simon Marchi
2017-02-08 12:40 ` Pedro Alves
2017-02-09 16:46 ` Simon Marchi
2017-02-09 17:53 ` Pedro Alves
2017-02-09 20:47 ` Eli Zaretskii
2017-02-22 21:06 ` Simon Marchi
2017-02-23 3:36 ` Eli Zaretskii
2017-02-23 15:57 ` Simon Marchi
2017-03-29 20:30 ` John Baldwin
2017-03-30 0:51 ` Simon Marchi [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=a6083dbb240011fe3de9834d0388bf66@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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