From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 772 invoked from network); 5 May 2023 00:38:32 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 5 May 2023 00:38:32 -0000 Received: (qmail 15976 invoked by uid 550); 5 May 2023 00:38:27 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 15880 invoked from network); 5 May 2023 00:38:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683247094; x=1685839094; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ilG+nZMcCfyiDAcavfCqV8I+dJfJy7X6wsuc44viVVo=; b=QKt6IMA6uogLEWLS5ydB5wE8uMe3qsrJvqB/c9jgzzX/nH6lwKu1LVBJbPSuhnhZEk zY4D/Dr7mnCNx0dkXib4wtN9KWlG/DOvlHRH7ymGMfrlQr5tOLLyVYan7EQFq9f7fel9 Jeb4k7/6AIPARSTWZpG11KmJPXE+R8WIYfyfaNsJhpdg9ArNkhu6X5aLD23U1w4sE2vo x24LQdH4tCusRLYV4TUiQK8h2pxsqGpYUGa3ZBOgH9+sSYOsEY5Rifkkl8aN1u64an7G UIirLywOQb0dXnAElsahs+RYMz4xFj7DCyoUtsxJIB7bOkvdy65p2wMlSbI0zmlrvobK v1lQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683247094; x=1685839094; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ilG+nZMcCfyiDAcavfCqV8I+dJfJy7X6wsuc44viVVo=; b=OkiTWjgTUV17Mk+tpcku2AfdJcxe4JZUpdQ4EPM3oIl1wevazO5JiVUXOKEjdhM720 oJ1eLvJk4SoLy8GfR6zrocoJYRQCEw3/pjjV+1qlWYo7gMNWYm5RdIbQGU6aVbbK91Dh IYT0mkIiKYSg0tf9iDhwQPWsFIkrxHKeakkPvr/WeovFySey8wvCRQDl8rdw6pr/T8sA g06m+VdPZ4bNkAPws5d8l46FD1uwRnRnu7jo3X1G3eHNGVOHpt5z5boV87i1nLMmU0Fi bs0S/XCu9723tN1J2q0li5EEfeFb/vBCsCwxpw5DVjYmcmF6fdTb9iqxvBm3qbVSQ34r ixCA== X-Gm-Message-State: AC+VfDz+h6jTM6BQKq2srrjr0z1Nu/6BzcxWCVGRkY8qyWs4iwjWYa5Z R/4uhXUWPrlqnmLzVSdybJVBEiZBegPrr+ZFhGRR5HmO/Uk= X-Google-Smtp-Source: ACHHUZ7CnIqdwF9NxLguml/QhTCJmDyvXJ+u7x+8jpU71B4TmCkkFVHGuPMzhvgnKwQeiNWro4/l0OueWpIi4rSuFNg= X-Received: by 2002:ac8:7c48:0:b0:3f2:113d:8a05 with SMTP id o8-20020ac87c48000000b003f2113d8a05mr45429qtv.47.1683247093967; Thu, 04 May 2023 17:38:13 -0700 (PDT) MIME-Version: 1.0 References: <20220923162518.56284329@inria.fr> <20221119153350.292e390b@inria.fr> <20230504081942.065fc12f@inria.fr> <20230504160304.GC4163@brightrain.aerifal.cx> <9ecc996a-5eba-404d-1b95-63398ea93543@gmail.com> In-Reply-To: <9ecc996a-5eba-404d-1b95-63398ea93543@gmail.com> From: JeanHeyd Meneide Date: Thu, 4 May 2023 20:37:58 -0400 Message-ID: To: musl@lists.openwall.com Cc: enh , Rich Felker , =?UTF-8?B?SuKCkeKCmeKCmyBHdXN0ZWR0?= , =?UTF-8?B?572X5YuH5YiaKFlvbmdnYW5nIEx1byk=?= , Jason Ekstrand Content-Type: multipart/alternative; boundary="0000000000001aee8505fae781fe" Subject: Re: [musl] C23 implications for C libraries --0000000000001aee8505fae781fe Content-Type: text/plain; charset="UTF-8" > for example, stuff like the %B specifier are technically optional given that the uppercase conversion specifier namespace wasn't reserved, but iirc there's no known implementation of C that uses it for any > other purpose. There was apparently one implementation that was already using %B as a kind of numeric printout (not for binary) that was reported during the meeting and at a few other junctures, so unfortunately it might not be fully portable. But, I think that for that implementation it's flag-guarded (though on by default). It'd be great if I remembered the name of the implementation (but the meeting this was discussed in was... over a year ago now? So I'd have to go back and refresh my memory). If I do remember, I thought to myself that I might send an e-mail asking them if they would feel okay with aligning their library with the standard's recommendations. Couldn't hurt to ask, right? - JeanHeyd --0000000000001aee8505fae781fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>=20 for example, stuff like the %B specifier are technically optional given that the uppercase conversion specifier namespace wasn't reserved, but iirc there's no known implementa= tion of C that uses it for any > other purpose.

= =C2=A0=C2=A0=C2=A0=C2=A0 There was apparently one implementation that was a= lready using %B as a kind of numeric printout (not for binary) that was rep= orted during the meeting and at a few other junctures, so unfortunately it = might not be fully portable. But, I think that for that implementation it&#= 39;s flag-guarded (though on by default). It'd be great if I remembered= the name of the implementation (but the meeting this was discussed in was.= .. over a year ago now? So I'd have to go back and refresh my memory). = If I do remember, I thought to myself that I might send an e-mail asking th= em if they would feel okay with aligning their library with the standard= 9;s recommendations. Couldn't hurt to ask, right?

- JeanHeyd
--0000000000001aee8505fae781fe--