mailing list of musl libc
 help / color / mirror / code / Atom feed
From: enh <enh@google.com>
To: musl@lists.openwall.com
Cc: Rob Landley <rob@landley.net>,
	Michael Jeanson <mjeanson@efficios.com>,
	 Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [musl] Re: sysconf(_SC_NPROCESSORS_CONF) broken.
Date: Fri, 29 Jul 2022 11:42:19 -0700	[thread overview]
Message-ID: <CAJgzZorKo6gW8QzFSxY9K-sgtrJgfi2Sf9paePW6DnyF9a_VVQ@mail.gmail.com> (raw)
In-Reply-To: <CAJgzZoqgabqj8yzHf0q-9GD3QSJVArDd6VGUp5B1NMpqu4=5UQ@mail.gmail.com>

done: https://android-review.googlesource.com/c/platform/bionic/+/2168844

what's the worst that could happen?


On Thu, Jul 28, 2022 at 10:27 AM enh <enh@google.com> wrote:
>
> 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
> <jonathan.rajotte-julien@efficios.com> wrote:
> >
> > Hi,
> >
> > >
> > > 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 [1].
> >
> > Which seems to be similar to what Vincent Donnefort, from [2], proposed.
> >
> > A follow up to unify our approach is also available here[3].
> >
> > [1] https://github.com/lttng/lttng-ust/commit/66dbdc3448a77043d0fd59f47b17e77a8d59fddb
> > [2] https://www.openwall.com/lists/musl/2021/07/06/2
> > [3] https://review.lttng.org/c/lttng-ust/+/8619
> >
> > Cheers

  reply	other threads:[~2022-07-29 18:42 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
2022-07-29 18:42         ` enh [this message]
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

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=CAJgzZorKo6gW8QzFSxY9K-sgtrJgfi2Sf9paePW6DnyF9a_VVQ@mail.gmail.com \
    --to=enh@google.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mjeanson@efficios.com \
    --cc=musl@lists.openwall.com \
    --cc=rob@landley.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).