From: enh <email@example.com>
Cc: Rob Landley <firstname.lastname@example.org>,
Michael Jeanson <email@example.com>,
Mathieu Desnoyers <firstname.lastname@example.org>
Subject: Re: [musl] Re: sysconf(_SC_NPROCESSORS_CONF) broken.
Date: Thu, 28 Jul 2022 10:27:12 -0700 [thread overview]
Message-ID: <CAJgzZoqgabqj8yzHf0q-9GD3QSJVArDd6VGUp5B1NMpqu4=5UQ@mail.gmail.com> (raw)
interesting... in case anyone's wondering why bionic didn't use
/sys/devices/system/cpu/possible, i didn't know it existed.
i'm pretty tempted to move us over to that. not because of the
distinction between "present" and "possible" -- i'm assuming over here
in mobile those two should always be the same anyway -- but because i
can just share code with "online" and do slightly less work than the
current directory scan...
On Wed, Jul 27, 2022 at 4:00 PM Jonathan Rajotte-Julien
> > i think the most recent thread on the topic:
> > https://www.openwall.com/lists/musl/2021/07/06/2
> > an older discussion is at
> > https://www.openwall.com/lists/musl/2019/03/15/5
> FIY, we recently had to revisit our handling of all this.
> See .
> Which seems to be similar to what Vincent Donnefort, from , proposed.
> A follow up to unify our approach is also available here.
>  https://github.com/lttng/lttng-ust/commit/66dbdc3448a77043d0fd59f47b17e77a8d59fddb
>  https://www.openwall.com/lists/musl/2021/07/06/2
>  https://review.lttng.org/c/lttng-ust/+/8619
next prev parent reply other threads:[~2022-07-28 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 6:28 [musl] " Rob Landley
2022-07-27 6:34 ` [musl] " Rob Landley
2022-07-27 17:58 ` Szabolcs Nagy
2022-07-27 21:29 ` Jonathan Rajotte-Julien
2022-07-28 17:27 ` enh [this message]
2022-07-29 18:42 ` enh
2022-07-29 18:53 ` NRK
2022-07-29 19:39 ` enh
2022-07-27 18:05 ` enh
2022-07-27 23:06 ` [musl] dynamic linker is capturing "reserved" library names erroneously Christopher Sean Morrison
2022-07-28 9:18 ` Szabolcs Nagy
2022-07-28 20:39 ` Christopher Sean Morrison
2022-07-29 0:07 ` Rich Felker
2022-07-29 6:19 ` Christopher Sean Morrison
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 NNTP newsgroup(s).