public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: DJ Delorie <dj@redhat.com>,
	libc-alpha@sourceware.org, linux-man@vger.kernel.org
Subject: Re: [patch v2] aligned_alloc: conform to C17
Date: Fri, 17 Mar 2023 22:10:52 +0100	[thread overview]
Message-ID: <ea4c6ddd-1db8-a005-7725-f30bc58e89f3@gmail.com> (raw)
In-Reply-To: <xnjzzf2oc3.fsf@greed.delorie.com>

Hi DJ

On 3/17/23 20:02, DJ Delorie via Libc-alpha wrote:
> Changes from v1:
> 
> * Fixed malloc-debug
> * alignment of zero is invalid
> * fixed ABI tables
> 
> References:
> https://patchwork.sourceware.org/project/glibc/patch/33ec9e0c1e587813b90e8aa771c2c8e6e379dd48.camel@posteo.net/
> https://sourceware.org/bugzilla/show_bug.cgi?id=20137
> https://sourceware.org/pipermail/libc-alpha/2023-February/145858.html
> 
> The memory.texi portion matches Martin's proposed patch.
> 
> man page portion, quoted to avoid CI/CD issues (I can send an official
> patch separately after the glibc patch is applied):

Please :)  Thanks!

BTW, I guess C11 was equivalent to C17 in this regard, or was this
changed in C17?

Cheers,

Alex

> 
>> diff --git a/man3/posix_memalign.3 b/man3/posix_memalign.3
>> index f5d6618b7..a73ff0421 100644
>> --- a/man3/posix_memalign.3
>> +++ b/man3/posix_memalign.3
>> @@ -91,9 +91,8 @@ The function
>>  is the same as
>>  .BR memalign (),
>>  except for the added restriction that
>> -.I size
>> -should be a multiple of
>> -.IR alignment .
>> +.I alignment
>> +must be a power of two.
>>  .PP
>>  The obsolete function
>>  .BR valloc ()

  reply	other threads:[~2023-03-17 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 19:02 DJ Delorie
2023-03-17 21:10 ` Alejandro Colomar [this message]
2023-03-17 21:15   ` DJ Delorie
2023-03-17 21:18     ` Alejandro Colomar
2023-03-17 22:01 ` Florian Weimer
2023-03-17 22:10   ` DJ Delorie
2023-03-17 22:40     ` Florian Weimer

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=ea4c6ddd-1db8-a005-7725-f30bc58e89f3@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.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).