From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] manual: Document __libc_single_threaded
Date: Thu, 21 May 2020 09:50:08 -0300 [thread overview]
Message-ID: <724ecd59-d6e4-9f52-f425-8a4ff795114f@linaro.org> (raw)
In-Reply-To: <2c218c9ed9586ed5491f6fa08045d1e883b126c3.1589998207.git.fweimer@redhat.com>
On 20/05/2020 15:12, Florian Weimer via Libc-alpha wrote:
> +@smallexample
> +if (__libc_single_threaded)
> + atomic_fetch_add (&reference_count, 1, memory_order_relaxed);
> +else
> + atomic_fetch_add (&reference_count, 1, memory_order_acq_rel);
> +@end smallexample
Shouldn't the access to __libc_single_threaded be atomic itself
(at least with relaxed semantic)?
next prev parent reply other threads:[~2020-05-21 12:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:12 [PATCH 0/2] Add __libc_single_threaded Florian Weimer via Libc-alpha
2020-05-20 18:12 ` [PATCH 1/2] Add the __libc_single_threaded variable Florian Weimer via Libc-alpha
2020-05-21 13:07 ` Szabolcs Nagy
2020-05-21 13:16 ` Florian Weimer via Libc-alpha
2020-05-21 13:26 ` Szabolcs Nagy
2020-05-20 18:12 ` [PATCH 2/2] manual: Document __libc_single_threaded Florian Weimer via Libc-alpha
2020-05-21 7:52 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-05-21 12:17 ` Florian Weimer via Libc-alpha
2020-05-21 11:18 ` Szabolcs Nagy
2020-05-21 12:16 ` Florian Weimer via Libc-alpha
2020-05-21 12:50 ` Adhemerval Zanella via Libc-alpha [this message]
2020-05-21 13:09 ` Szabolcs Nagy
2020-05-21 13:15 ` Adhemerval Zanella via Libc-alpha
2020-05-21 13:30 ` Szabolcs Nagy
2020-05-21 13:44 ` Florian Weimer via Libc-alpha
2020-05-21 13:58 ` Adhemerval Zanella via Libc-alpha
2020-05-21 14:03 ` Florian Weimer via Libc-alpha
2020-05-22 10:01 ` Szabolcs Nagy
2020-05-22 10:05 ` Florian Weimer via Libc-alpha
2020-05-22 10:54 ` Szabolcs Nagy
2020-05-22 11:08 ` Florian Weimer via Libc-alpha
2020-05-22 15:07 ` Rich Felker
2020-05-22 16:14 ` Rich Felker
2020-05-22 16:36 ` Adhemerval Zanella via Libc-alpha
2020-05-22 17:02 ` Florian Weimer via Libc-alpha
2020-05-22 17:18 ` Florian Weimer via Libc-alpha
2020-05-22 17:28 ` Rich Felker
2020-05-22 17:40 ` Florian Weimer via Libc-alpha
2020-05-22 17:49 ` Rich Felker
2020-05-22 19:22 ` Szabolcs Nagy
2020-05-22 19:53 ` Rich Felker
2020-05-23 6:49 ` Szabolcs Nagy
2020-05-23 16:02 ` Rich Felker
2020-05-25 8:08 ` Florian Weimer via Libc-alpha
2020-05-25 8:08 ` Florian Weimer via Libc-alpha
2020-05-25 17:21 ` Rich Felker
2020-05-27 11:54 ` Florian Weimer via Libc-alpha
2020-05-27 15:36 ` Rich Felker
2020-06-03 15:00 ` Florian Weimer via Libc-alpha
2020-06-03 17:11 ` Rich Felker
2020-05-21 13:56 ` Adhemerval Zanella via Libc-alpha
2020-05-21 13:14 ` Florian Weimer via Libc-alpha
2020-05-21 14:32 ` Adhemerval Zanella via Libc-alpha
2020-06-03 15:48 ` Florian Weimer via Libc-alpha
2020-06-03 17:52 ` Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=724ecd59-d6e4-9f52-f425-8a4ff795114f@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.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).