This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] [BZ 18034] [AArch64] Lazy TLSDESC relocation data race fix
- From: Torvald Riegel <triegel at redhat dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, Marcus Shawcroft <Marcus dot Shawcroft at arm dot com>, Ramana Radhakrishnan <Ramana dot Radhakrishnan at arm dot com>
- Date: Fri, 24 Apr 2015 19:40:38 +0200
- Subject: Re: [PATCH] [BZ 18034] [AArch64] Lazy TLSDESC relocation data race fix
- Authentication-results: sourceware.org; auth=none
- References: <553793A3 dot 7030206 at arm dot com> <1429718899 dot 6557 dot 17 dot camel at triegel dot csb> <5537D6F8 dot 1030509 at arm dot com> <1429825616 dot 6557 dot 37 dot camel at triegel dot csb> <553A2374 dot 2000004 at arm dot com>
On Fri, 2015-04-24 at 12:05 +0100, Szabolcs Nagy wrote:
>
> On 23/04/15 22:46, Torvald Riegel wrote:
> > On Wed, 2015-04-22 at 18:14 +0100, Szabolcs Nagy wrote:
> >> (the particular case i'm trying to fix is hard because
> >> the access to td->entry is generated by the compiler, so
> >> it has to be worked around inside the entry function.
> >> i think x86 does not have this issue)
> >
> > Do you mean that you want to affect the compiler-generated code after it
> > has been generated?
> >
>
> i'm fixing the tlsdesc entry functions in libc
>
Sorry, I'm still not sure I can follow. IIUC, the compiler-generated
asm code for TLS accesses may lack acquire barriers in some cases. Do
you want to work around that by trying to adapt the glibc
implementation, or do you just want to fix all glibc-specific bugs, and
handle the compiler-side issues separately?