From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 Received: (qmail 6463 invoked from network); 14 Apr 2020 16:55:20 -0000 Received-SPF: pass (mother.openwall.net: domain of lists.openwall.com designates 195.42.179.200 as permitted sender) receiver=inbox.vuxu.org; client-ip=195.42.179.200 envelope-from= Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with UTF8ESMTPZ; 14 Apr 2020 16:55:20 -0000 Received: (qmail 7283 invoked by uid 550); 14 Apr 2020 16:55:18 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 7265 invoked from network); 14 Apr 2020 16:55:17 -0000 From: Florian Weimer To: Rich Felker Cc: musl@lists.openwall.com, Norbert Lange References: <20200409181824.GD13749@port70.net> <87r1wwik8t.fsf@mid.deneb.enyo.de> <20200410010255.GN11469@brightrain.aerifal.cx> <877dyinzuz.fsf@mid.deneb.enyo.de> <20200414155522.GB11469@brightrain.aerifal.cx> Date: Tue, 14 Apr 2020 18:55:06 +0200 In-Reply-To: <20200414155522.GB11469@brightrain.aerifal.cx> (Rich Felker's message of "Tue, 14 Apr 2020 11:55:22 -0400") Message-ID: <87wo6iknx1.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [musl] [BUG] sysconf implementing _SC_NPROCESSORS_(CONF|ONLN) incorrectly * 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.