Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211123201438.GA7074@brightrain.aerifal.cx>
Date: Tue, 23 Nov 2021 15:14:38 -0500
From: Rich Felker <dalias@...c.org>
To: Florian Weimer <fweimer@...hat.com>
Cc: musl@...ts.openwall.com
Subject: Re: __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

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.