[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150310011949.GA23507@brightrain.aerifal.cx>
Date: Mon, 9 Mar 2015 21:19:49 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: pthread object sizes for new archs
On Mon, Mar 09, 2015 at 09:07:33PM -0400, Rich Felker wrote:
> What I'd like to propose is that, for all new archs, we ignore the
> glibc-provided size of the pthread types and stick with the baseline
> 32-bit sizes, enlarged only by the plausible number of fields that
> could need to be pointers if the arch is 64-bit. For mutexes, I'd like
> to stick to 32 bytes (33% increase going from 32-bit to 64-bit), but
> 40 (66% increase) wouldn't be horrible. The glibc aarch64 64-bit bloat
> cost of 100% is ridiculous though.
Note that for x32, this would mean discarding the size fix recently
made as commit e7b9887e8b65253087ab0b209dc8dd85c9f09614 and changing
all the pthread object sizes on x32 to match all the plain 32-bit
archs.
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.
