From: John Baldwin <jhb@FreeBSD.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Note support for TLS variables on FreeBSD.
Date: Mon, 25 Mar 2019 19:27:00 -0000 [thread overview]
Message-ID: <6338e5f0-eca8-3592-e918-004a4c594a0e@FreeBSD.org> (raw)
In-Reply-To: <20190312211632.48128-1-jhb@FreeBSD.org>
On 3/12/19 2:16 PM, John Baldwin wrote:
> gdb/ChangeLog:
>
> * NEWS: Mention TLS support for FreeBSD.
> ---
> gdb/ChangeLog | 4 ++++
> gdb/NEWS | 5 +++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index eea9ecfde9..b7df439ddc 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,7 @@
> +2019-03-12 John Baldwin <jhb@FreeBSD.org>
> +
> + * NEWS: Mention TLS support for FreeBSD.
> +
> 2019-03-12 John Baldwin <jhb@FreeBSD.org>
>
> * NEWS: Combine separate "New targets" sections for 8.3.
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 88ce9a7104..76a33cca5c 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,11 @@
>
> *** Changes since GDB 8.3
>
> +* GDB now supports Thread Local Storage (TLS) variables on several
> + FreeBSD architectures (amd64, i386, powerpc, riscv). Other
> + architectures require kernel changes. TLS is not yet supported for
> + amd64 and i386 process core dumps.
> +
> *** Changes in GDB 8.3
>
> * GDB and GDBserver now support access to additional registers on
>
Eli,
I know you've been busy with the threads on style stuff for 8.3, but can
you look this over when you get a chance? Thanks.
--
John Baldwin
next prev parent reply other threads:[~2019-03-25 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:20 John Baldwin
2019-03-25 19:27 ` John Baldwin [this message]
2019-03-25 20:09 ` Eli Zaretskii
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=6338e5f0-eca8-3592-e918-004a4c594a0e@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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