mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: [musl] C23: other last minute changes
Date: Sun, 25 Jun 2023 09:48:18 +0200	[thread overview]
Message-ID: <20230625094818.5e6b156c@inria.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]

Hello,
there were other last minute (in the literal sense of the term)
changes to C23 that might impact musl. I updated the summary page at

        https://gustedt.gitlabpages.inria.fr/c23-library/

As far as I can see these are

   - `PRI` macros for narrow types now have to be exact, musl does not
     seem to conform to this new requirement

   - the `lc` specifier for `printf` does print NUL for a nul
     character, we already talked about this

For the first, a change is conforming to C17 so it can be done
immediately without problems. The second is in principle a normative
change in C and in POSIX, but it seems that all other POSIX
implementations already are doing this, so probably we should just
fall in line.

There are also

   - `mktime` and `timegm` are not supposed to change `tm_wday` if the
     conversion fails

   - `fputwc` now also sets the error indicator of the stream if an
     encoding error occurs. This was previously already required by
     POSIX.

I don't think that musl has problems here

Jₑₙₛ

-- 
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Université de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA Nancy Grand Est :::::::::::::::::::::::: Camus ::
:: :::::::::::::::::::::::::::::::::::: ☎ +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2023-06-25  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  7:48 Jₑₙₛ Gustedt [this message]
2023-06-25 15:24 ` Rich Felker
2023-06-25 18:38   ` Jₑₙₛ Gustedt

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=20230625094818.5e6b156c@inria.fr \
    --to=jens.gustedt@inria.fr \
    --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).