public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] New internal function __access_noerrno
Date: Sat, 19 Nov 2016 03:09:00 -0000	[thread overview]
Message-ID: <9884af89-48ab-c1ab-5b3b-f88b4f4b820f@gotplt.org> (raw)
In-Reply-To: <0b12c716-a973-8cad-4982-216fd0a1495e@linaro.org>

On Saturday 19 November 2016 12:23 AM, Adhemerval Zanella wrote:
> I think it might be an issue depending of whether errno is accessible
> on tunables initialization (it might be the case where is not yet

That is correct.  Tunables initialization happens very early, earlier
than TLS setup and errno is a TLS variable.

Siddhesh

  reply	other threads:[~2016-11-19  3:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 17:04 [PATCH 1/2] Consolidate Linux access implementation Adhemerval Zanella
2016-11-10 17:04 ` [PATCH 2/2] New internal function __access_noerrno Adhemerval Zanella
2016-11-10 17:12   ` Andreas Schwab
2016-11-10 18:26     ` Adhemerval Zanella
2016-11-10 17:53   ` Siddhesh Poyarekar
2016-11-10 18:31     ` Adhemerval Zanella
2016-11-16 13:27       ` Adhemerval Zanella
2016-11-16 13:44         ` Adhemerval Zanella
2016-11-16 16:27           ` Carlos O'Donell
2016-11-16 18:29             ` Joseph Myers
2016-11-17 20:53           ` Kalle Olavi Niemitalo
2016-11-17 21:30             ` Adhemerval Zanella
2016-11-18  0:21               ` Kalle Olavi Niemitalo
2016-11-18 18:54                 ` Adhemerval Zanella
2016-11-19  3:09                   ` Siddhesh Poyarekar [this message]
2016-11-21  5:12         ` Kalle Olavi Niemitalo
2016-11-21 12:45           ` Adhemerval Zanella
2016-11-10 17:44 ` [PATCH 1/2] Consolidate Linux access implementation Siddhesh Poyarekar
2016-11-16 13:16 ` Carlos O'Donell

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=9884af89-48ab-c1ab-5b3b-f88b4f4b820f@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    /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).