This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Async signal safe TLS accesses
- From: Rich Felker <dalias at aerifal dot cx>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Andrew Hunter <ahh at google dot com>, GNU C Library <libc-alpha at sourceware dot org>, Paul Pluzhnikov <ppluzhnikov at google dot com>
- Date: Fri, 6 Dec 2013 22:04:06 -0500
- Subject: Re: [PATCH] Async signal safe TLS accesses
- Authentication-results: sourceware.org; auth=none
- References: <CALoOobP6rTDosadvLKhHY+deDsU-FtvyO8QX_Y4dZy716e2ATQ at mail dot gmail dot com> <1386273671-13010-1-git-send-email-ahh at google dot com> <52A2475F dot 20303 at redhat dot com> <CADroS=7TtPaxpADezQ+U-NGrbF_iBVCaX8_g1pK+m54KTBSyAA at mail dot gmail dot com> <52A26025 dot 4020008 at redhat dot com>
On Fri, Dec 06, 2013 at 06:39:17PM -0500, Carlos O'Donell wrote:
> > Open to other suggestions as well.
>
> Yes, I suggest:
>
> - Declare GNU2 dialect TLS symbols AS-unsafe for the time being
> and tackle it later.
I'm fine with this as long as "later" is defined as "right away once
the non-GNU2-dialect AS-safety work is committed. :-) In other words,
I don't think deficiencies in the GNU2 dialect code should block
getting the work that's already been done committed, but I don't want
to see it forgotten about anyway, since the trend seems to be towards
moving to GNU2 dialect (IIRC some archs even use it by default).
Rich