public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 4/4] malloc: alignment might change in future versions
Date: Thu, 26 Feb 2026 10:41:21 -0800	[thread overview]
Message-ID: <3e150b62-ffb6-4a6c-88f9-b34dac5c5cf1@cs.ucla.edu> (raw)
In-Reply-To: <lhu342nn01s.fsf@oldenburg.str.redhat.com>

On 2026-02-26 04:47, Florian Weimer wrote:
>> --- a/manual/lang.texi
>> +++ b/manual/lang.texi
>> @@ -597,7 +597,7 @@ types have a fundamental alignment and lack stricter alignment specifiers.
>>   In @theglibc{}, the value of @code{alignof (max_align_t)} is 16 on
>>   most architectures.  However, it is 8 on 32-bit architectures that do
>>   not require 16-byte alignment from @code{malloc} to support predefined
>> -types.
>> +types.  The value may change in future releases.
> Can we really change the definition of the type, though?  That's close
> to an ABI event.
> 
> Rest looks okay to me.

Thanks, I installed the patches without that sentence.

However, the manual should discuss the ABI effect of any possible 
differences in max_align_t, or in intmax_t/uintmax_t for that matter. 
This is relevant partly because C23 (unlike earlier C standards) allows 
intmax_t to be narrower than int128_t (assuming the latter type exists, 
which it really should with GCC).

I'll propose further patches along those lines.

  reply	other threads:[~2026-02-26 18:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 18:18 [PATCH v3 0/4] malloc doc fixes for alignment Paul Eggert
2026-02-12 18:18 ` [PATCH v3 1/4] Document max_align_t Paul Eggert
2026-02-26 12:41   ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 2/4] Document malloc alignment Paul Eggert
2026-02-26 12:53   ` Florian Weimer
2026-02-26 12:56     ` Florian Weimer
2026-02-26 13:17       ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 3/4] Say malloc (0) != NULL is now common; resection Paul Eggert
2026-02-26 13:15   ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 4/4] malloc: alignment might change in future versions Paul Eggert
2026-02-26 12:47   ` Florian Weimer
2026-02-26 18:41     ` Paul Eggert [this message]
2026-02-26 18:38       ` [PATCH 1/2] doc: document max_align_t effect on ABI Paul Eggert
2026-02-26 18:38         ` [PATCH 2/2] doc: document C23 changes to intmax_t Paul Eggert
2026-02-13 16:28 [PATCH v3 4/4] malloc: alignment might change in future versions Wilco Dijkstra

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=3e150b62-ffb6-4a6c-88f9-b34dac5c5cf1@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).