public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org
Subject: Re: [patch] aligned_alloc: conform to C17
Date: Fri, 17 Mar 2023 15:55:54 -0400	[thread overview]
Message-ID: <xnfsa32lv9.fsf@greed.delorie.com> (raw)
In-Reply-To: <7c6b7579-e6ce-c6c4-cc97-957967849613@cs.ucla.edu>

Paul Eggert <eggert@cs.ucla.edu> writes:
> As you mention the C17 wording is not entirely clear, but it's 
> implausible that the standardizers intended 0 to be a valid alignment: 
> if they had intended that they would have said so clearly.

I think I was trying to agree with you, using more than "that makes
sense" :-)

The "char align is weakest" statement seems to be the key one.


  reply	other threads:[~2023-03-17 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 20:48 DJ Delorie
2023-03-16 21:00 ` Adhemerval Zanella Netto
2023-03-17  0:00   ` DJ Delorie
2023-03-17  6:33     ` Paul Eggert
2023-03-17 19:55       ` DJ Delorie [this message]
2023-03-16 22:00 ` Paul Eggert

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=xnfsa32lv9.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=eggert@cs.ucla.edu \
    --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).