public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	Torvald Riegel <triegel@redhat.com>,
	nd@arm.com, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [RFC][BZ #19329] high level description of pthread_create vs dlopen races
Date: Tue, 06 Dec 2016 18:31:00 -0000	[thread overview]
Message-ID: <20161206183110.GA16379@port70.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1612061745280.16077@digraph.polyomino.org.uk>

* Joseph Myers <joseph@codesourcery.com> [2016-12-06 17:47:45 +0000]:
> On Tue, 6 Dec 2016, Szabolcs Nagy wrote:
> 
> > meanwhile the rest of the world needs a way to detect
> > reentry into an as-safe library call which currently
> > requires as-safe tls (signal mask is not an option:
> > syscalls are too slow) and a way to do soft float
> > correctly (fenv is tls and arithmetics must be as-safe)
> > or just access errno (which could be made as-safe even
> > if tls access is not as-safe otherwise, but specifying
> > that correctly in the standard is more hassle than
> > requiring all tls access to be as-safe).
> 
> errno, the powerpc soft-float floating-point environment and the libdfp 
> soft-dfp decimal rounding mode are all initial-exec TLS (and other cases 
> of floating-point environment are hardware registers rather than TLS 
> variables).  Does being initial-exec help?
> 

yes, that works.

only tls access through __tls_get_addr may be
non-as-safe now.

(but if a language standard does not guarantee tls
access to be as-safe then implementation behaviour
does not help portable code.)

  reply	other threads:[~2016-12-06 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 19:03 Szabolcs Nagy
2016-12-05 19:24 ` Torvald Riegel
2016-12-06 17:23   ` Szabolcs Nagy
2016-12-06 17:48     ` Joseph Myers
2016-12-06 18:31       ` Szabolcs Nagy [this message]
2016-12-07 14:08     ` Torvald Riegel
2016-12-21 15:27       ` Szabolcs Nagy
2017-01-05 17:53         ` Szabolcs Nagy

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=20161206183110.GA16379@port70.net \
    --to=nsz@port70.net \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=szabolcs.nagy@arm.com \
    --cc=triegel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).