From: Kevin Buettner <kevinb@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5 00/11] GDB-internal TLS support for Linux targets
Date: Mon, 24 Feb 2025 13:29:41 -0700 [thread overview]
Message-ID: <20250224132941.7473517b@f41-zbm-amd> (raw)
In-Reply-To: <87ikp38hsm.fsf@tromey.com>
Hi Tom,
On Fri, 21 Feb 2025 07:59:53 -0700
Tom Tromey <tom@tromey.com> wrote:
> >>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>
> Kevin> This series of commits adds internal TLS lookup support to GDB for the
> Kevin> following Linux target architectures: x86_64, aarch64, ppc64, s390x,
> Kevin> and riscv. When available, libthread_db support for TLS lookup is
> Kevin> still preferred/used since it should be more accurate. This means
> Kevin> that existing TLS support will still work as it did before - this new
> Kevin> TLS support will only be used when libthread_db TLS support is not
> Kevin> available. (Though it is possible to force internal TLS support to be
> Kevin> used via a new maintenance command).
>
> Thanks for doing this.
> I skimmed this series but didn't really review it in depth.
> I think you should go ahead and check it in though.
Thanks for looking over!
I'll wait a week for objections, after which I'll push this series.
Kevin
next prev parent reply other threads:[~2025-02-24 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 17:45 Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 01/11] Don't attempt to find TLS address when target has no registers Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 02/11] Allow TLS access to work in gdb.server/no-thread-db.exp Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 03/11] Track and fetch TLS module ids for MUSL and GLIBC Kevin Buettner
2025-02-26 15:18 ` Andrew Burgess
2025-01-31 17:45 ` [PATCH v5 04/11] Implement internal TLS address lookup for Linux targets Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 05/11] Internal TLS support for aarch64, x86_64, riscv, ppc64, and s390x Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 06/11] Internal, but disabled, TLS support for i386 Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 07/11] Delete disabled i386 internal TLS support Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 08/11] New test - gdb.base/tls-nothreads.exp Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 09/11] New test - gdb.base/tls-multiobj.exp Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 10/11] New test - gdb.base/tls-dlobj.exp Kevin Buettner
2025-01-31 17:45 ` [PATCH v5 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command Kevin Buettner
2025-02-21 14:59 ` [PATCH v5 00/11] GDB-internal TLS support for Linux targets Tom Tromey
2025-02-24 20:29 ` Kevin Buettner [this message]
2025-02-26 16:49 ` Andrew Burgess
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=20250224132941.7473517b@f41-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--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