From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: max_align_t mess on i386
Date: Sun, 15 Dec 2019 13:04:32 -0500 [thread overview]
Message-ID: <20191215180432.GZ1666@brightrain.aerifal.cx> (raw)
In-Reply-To: <871rt6eqx5.fsf@mid.deneb.enyo.de>
On Sat, Dec 14, 2019 at 06:51:50PM +0100, Florian Weimer wrote:
> * Rich Felker:
>
> > However, whatever we do with i386, the option of using 8-byte
> > granularity remains open for all the other 32-bit archs, most of which
> > tend to be used with machines far more memory-constrained than i386.
>
> Note that powerpc has a similar issue, but with long double:
>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=6527>
>
> But perhaps musl follows the old powerpc ABI, where double and long
> double are both binary64 (I have not checked, sorry).
One thing we should consider though: since presumably the psABI has
max_align_t as 16-byte alignment on powerpc now, if we increase i386
should we also increase powerpc? Even though there's no type actually
depending on it? This also applies to powerpc64 too, I think, which is
an arch not being affected by time64 change.
Rich
next prev parent reply other threads:[~2019-12-15 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 15:19 Rich Felker
2019-12-14 17:51 ` Florian Weimer
2019-12-14 18:17 ` Rich Felker
2019-12-14 18:53 ` Daniel Kolesa
2019-12-15 18:04 ` Rich Felker [this message]
2019-12-15 5:47 ` Markus Wichmann
2019-12-15 18:06 ` Jeffrey Walton
2019-12-15 18:22 ` Rich Felker
2019-12-16 15:30 ` Jeffrey Walton
2019-12-16 15:56 ` Rich Felker
2019-12-16 16:36 ` Jeffrey Walton
2019-12-16 17:49 ` Rich Felker
2019-12-16 16:40 ` Florian Weimer
2019-12-16 17:45 ` Rich Felker
2019-12-16 17:49 ` Florian Weimer
2019-12-16 17:51 ` Rich Felker
2019-12-15 18:23 ` Joakim Sindholt
2019-12-15 18:51 ` Rich Felker
2019-12-15 20:03 ` Alexander Monakov
2019-12-15 20:50 ` Szabolcs Nagy
2019-12-15 21:51 ` Jeffrey Walton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191215180432.GZ1666@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).