From: Simon Marchi <simon.marchi@polymtl.ca>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove support for using the bsd-uthread target on FreeBSD.
Date: Tue, 04 Apr 2017 19:52:00 -0000 [thread overview]
Message-ID: <464e26c426c0486211bed1892a278f86@polymtl.ca> (raw)
In-Reply-To: <20170404183801.17957-1-jhb@FreeBSD.org>
On 2017-04-04 14:38, John Baldwin wrote:
> The bsd-uthread target supports an old thread library ("libc_r") that
> was last included in FreeBSD release 6.4 released in 2008. However,
> this library has not been used as the default library since FreeBSD
> 5.0 (2003) and 4.11 (2005). Thread support for modern FreeBSD binaries
> is provided via "normal" LWP support in core files and the native
> FreeBSD target.
Thanks again!
By any chance, would you know the same information but for obsd and
nbsd? If not I'll inquire on the relevant mailing lists.
Simon
next prev parent reply other threads:[~2017-04-04 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 18:43 John Baldwin
2017-04-04 19:52 ` Simon Marchi [this message]
2017-04-04 21:28 ` John Baldwin
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=464e26c426c0486211bed1892a278f86@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
/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