From: Florian Weimer <fw@deneb.enyo.de>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com, Norbert Lange <nolange79@gmail.com>
Subject: Re: [musl] [BUG] sysconf implementing _SC_NPROCESSORS_(CONF|ONLN) incorrectly
Date: Tue, 14 Apr 2020 18:55:06 +0200 [thread overview]
Message-ID: <87wo6iknx1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200414155522.GB11469@brightrain.aerifal.cx> (Rich Felker's message of "Tue, 14 Apr 2020 11:55:22 -0400")
* Rich Felker:
> On Tue, Apr 14, 2020 at 12:08:52PM +0200, Florian Weimer wrote:
>> * Rich Felker:
>>
>> >> For glibc, we had to change our logic to artificially inflate the CPU
>> >> to 2 if we cannot determine it, as the more conservative choice.
>> >
>> > Wait, you mean some software is abusing these interfaces to omit
>> > memory barriers or something? *facepalm* *sigh*
>>
>> Yes, indeed. glibc itself parses uname -v output for this purpose
>> (something we should probably remove, too).
>
> I don't understand. Certainly it's not executing a child process at
> runtime. Do you mean SYS_uname or are you talking about guessing
> number of cpus for parallel build at make time or something?
I meant the string that is printed by uname -v. The internal
implementation is of course different.
next prev parent reply other threads:[~2020-04-14 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 10:29 Norbert Lange
2020-04-09 18:18 ` Szabolcs Nagy
2020-04-09 18:31 ` Florian Weimer
2020-04-10 1:02 ` Rich Felker
2020-04-14 10:08 ` Florian Weimer
2020-04-14 15:55 ` Rich Felker
2020-04-14 16:55 ` Florian Weimer [this message]
2020-04-15 9:38 ` Norbert Lange
2020-04-15 9:50 ` Florian Weimer
2020-04-15 9:57 ` Norbert Lange
2020-04-15 10:04 ` Szabolcs Nagy
2020-04-15 16:01 ` Rich Felker
2020-04-15 15:58 ` Rich Felker
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=87wo6iknx1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=nolange79@gmail.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.
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).