From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28273 invoked from network); 23 Nov 2021 20:14:54 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 23 Nov 2021 20:14:54 -0000 Received: (qmail 14029 invoked by uid 550); 23 Nov 2021 20:14:52 -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 14003 invoked from network); 23 Nov 2021 20:14:51 -0000 Date: Tue, 23 Nov 2021 15:14:38 -0500 From: Rich Felker To: Florian Weimer Cc: musl@lists.openwall.com Message-ID: <20211123201438.GA7074@brightrain.aerifal.cx> References: <875ysips53.fsf@oldenburg.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <875ysips53.fsf@oldenburg.str.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] __WORDSIZE on x32 On Tue, Nov 23, 2021 at 08:51:36PM +0100, Florian Weimer wrote: > This looks a bid suspicious: Come on, you missed a chance to say "sus". :-) > arch/x32/bits/reg.h:#undef __WORDSIZE > arch/x32/bits/reg.h:#define __WORDSIZE 32 > arch/x32/bits/user.h:#undef __WORDSIZE > arch/x32/bits/user.h:#define __WORDSIZE 64 > > I don't know if it causes any actual problems. I discovered it while > checking whether musl defines/uses __WORDSIZE. Thanks for the find. Now... which is it supposed to be? commit 664cd341921007cea52c8891f27ce35927dca378 introduced x32 as a patch against a copy of x86_64 and changed one instance from 64 to 32, so presumably the intent was to change both. Is this in agreement with what it means on glibc or elsewhere? Rich