From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix TLS access for -static -pthread
Date: Tue, 20 May 2014 15:18:00 -0000 [thread overview]
Message-ID: <20140520151754.GA27490@host2.jankratochvil.net> (raw)
In-Reply-To: <878upwtris.fsf@fleche.redhat.com>
On Tue, 20 May 2014 17:10:35 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> On Thu, 10 Apr 2014 13:52:04 +0200, Jan Kratochvil wrote:
> >> Future glibcs may implement more native support for -static -pthread TLS
> >> https://sourceware.org/bugzilla/show_bug.cgi?id=16828
> >> which will require also some new GDB support.
>
> Jan> Posted now by Carlos O'Donell:
> Jan> [PATCH] Initialize _r_debug for static applications.
> Jan> https://sourceware.org/ml/libc-alpha/2014-04/msg00183.html
> Jan> Message-ID: <5347321E.2060802@redhat.com>
>
> Does this negate the need for the previous patch?
No.
> Or merely mean that an additional patch is desirable?
Yes, filed for GDB such additional patch request as:
Improve TLS variables glibc compatibility
https://sourceware.org/bugzilla/show_bug.cgi?id=16954
Jan
next prev parent reply other threads:[~2014-05-20 15:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 11:52 Jan Kratochvil
2014-04-11 11:03 ` Jan Kratochvil
2014-05-20 15:10 ` Tom Tromey
2014-05-20 15:18 ` Jan Kratochvil [this message]
2014-05-20 15:10 ` Tom Tromey
2014-05-21 12:17 ` Jan Kratochvil
2014-05-21 14:14 ` Tom Tromey
2014-05-21 14:28 ` [commit] " Jan Kratochvil
2014-06-05 7:17 ` Yao Qi
2014-06-05 8:06 ` Jan Kratochvil
2014-06-05 9:32 ` Yao Qi
2014-06-05 9:39 ` Jan Kratochvil
2014-06-05 14:20 ` Yao Qi
2014-06-05 15:23 ` Pedro Alves
2014-06-06 2:26 ` Yao Qi
2014-06-05 15:18 ` Pedro Alves
2014-06-06 15:03 ` Jan Kratochvil
2014-06-06 2:36 ` Yao Qi
2014-06-06 6:16 ` Yao Qi
2014-06-06 14:20 ` Jan Kratochvil
2014-06-06 5:34 ` Sergio Durigan Junior
2014-06-06 14:21 ` Jan Kratochvil
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=20140520151754.GA27490@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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