Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 16 Dec 2019 12:51:24 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: max_align_t mess on i386

On Mon, Dec 16, 2019 at 06:49:21PM +0100, Florian Weimer wrote:
> * Rich Felker:
> 
> > The latter looks buggy. It's clearly supposed to be in bits, not
> > bytes, with some archs defining it as 64 or 128 and:
> >
> > gcc/defaults.h:#ifndef MALLOC_ABI_ALIGNMENT
> > gcc/defaults.h:#define MALLOC_ABI_ALIGNMENT BITS_PER_WORD
> >
> > However arm has:
> >
> > gcc/config/arm/arm.h:#define MALLOC_ABI_ALIGNMENT  BIGGEST_ALIGNMENT
> >
> > which is in bytes...
> 
> The target hook is in bits.  The macro synthesized from that is in
> bytes:
> 
>   cpp_define_formatted (pfile, "__BIGGEST_ALIGNMENT__=%d",
>                         BIGGEST_ALIGNMENT / BITS_PER_UNIT);

Ah, that explains it. So no bug. Thanks.

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.