From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) by sourceware.org (Postfix) with ESMTPS id 2C5C7381A89C for ; Fri, 28 Jun 2024 22:02:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2C5C7381A89C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2C5C7381A89C Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::331 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1719612125; cv=none; b=sIOQK02bzs3r8N5FFU6uBlFex+ZshoI/5COi8uMQ5i7RpktUO4dqkf7M9wbVEzoB1KV8HyX09yKmVZDa7gU+Dn8H74/NR6jzukxImvtRHahXs7YWFCB/z/6Lj8L25SnzqUsVP3MXeDMdI4+YM60XGgedO2oX9zW8fkodMJqACPk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1719612125; c=relaxed/simple; bh=v6fnmMlm7LC87cWemwymS7w9NztuqctrlXRUziOVMc0=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=EJJ+9tD6zoNJIpXLEB2a4fdcdQoUjwR76wfhMpSwk4PlWBZUEGt+Ctrqp9YtLFLgDTdvMd/GYSuNbkdySCGFIFsCq53VWBP+uZ/WKUzmg8S1eMDo1oFnWknZAQRrl193dxrm+Fo20BFKbr8SnJREa7chqistxNnylfo7loFXUqA= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ot1-x331.google.com with SMTP id 46e09a7af769-702041ba5aaso2617a34.1 for ; Fri, 28 Jun 2024 15:02:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719612122; x=1720216922; darn=sourceware.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=BQjULnxzM9sPHp55p09a0FaT0cgcbsFAoXqbXUhzBDE=; b=m54HJKvCkmxhTbOa3cMGbkhYK6y+l3T2RjKExV4ZwZ+LhLxwGr7aMJCpffAsDiqF98 jjKLUTC4BH2JO8qu+h9LsfSshYMOaNUzjAuy70u934LeBIB9y/EW5pva7p8cgKAYyzlV Rls559A1ygjqqYd1Jg/0j0SC/yC+b0NTs2LgD9CHjlT1XYWt5xaClPAiIm1B6iuHUuKs xwr5yFoMG9QOCtfDXx+moCVHO49BVQpiMEtJjTTFTiGu+Nz4ulvKP1KkoZofqXVxY+rJ Fq0i0F66MMyFLNlaOKEEpiqLYaOHrvCzhNFU9SVspR7Z1wGh2Cfg77fTkWzJYD+kjGR1 AObg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719612122; x=1720216922; h=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=BQjULnxzM9sPHp55p09a0FaT0cgcbsFAoXqbXUhzBDE=; b=vloYH15+oWwG4zGLfoOaW4QZX/FlpqVMPC8JOjcxS7EXNl6Mzviy3AhjU+zRyS91HU 756l7re46FFyvQM0hAC0S7Icez+PHcbZwNoM1dD91dM0y/Zq9wyzljHpPcjlOGICtdSw WOrPmDTQcimlV6I7eD2vHVZZiz8Yzuib5WtMDxoZ/rdMiN5M8r0Qa2n76IkT13yKR0DR i1cX/LLlKsHAkrXDtW3/h04JS2X7F48oEE7x/ZFwBaEQHhX8En+8x/CTw+VMqDIO3LDm NZTtM4i16wLRvdG76VPPowm7DzTWFvvA3pRYb/PyVhtJSwQeK2xS5+h4DS6od9hyKVul fvfQ== X-Gm-Message-State: AOJu0Yx4F1EWE55CBybuKhdiFevsilZflvVDnLqSoR81UKOLV30crQRQ m9q5CpliE21vnkt2sfJ+MA7OIaQbhaNMkE3ybBCUAzekBgAXCMnopqD3YEqvz01UFEuGI/tcmTs vadZjf4g7oFaQ2d5Z6RW28cQp3uXl62gc X-Google-Smtp-Source: AGHT+IFQsGj6T+OelKbXpX0y6BTTOsLUx+idMU7d01Oh2T6opjBbaThH4thedxyFh9dINLcDDXyTCBdZlPlcMJI4AOE= X-Received: by 2002:a9d:7c95:0:b0:700:d299:1f25 with SMTP id 46e09a7af769-700d5c63451mr9251800a34.34.1719612121894; Fri, 28 Jun 2024 15:02:01 -0700 (PDT) MIME-Version: 1.0 References: <8128b808-e10d-483d-b9ee-539fa0dc8d49@systematicsw.ab.ca> In-Reply-To: <8128b808-e10d-483d-b9ee-539fa0dc8d49@systematicsw.ab.ca> From: Joel Sherrill Date: Fri, 28 Jun 2024 17:01:50 -0500 Message-ID: Subject: Re: C11/POSIX-2024 Questions To: newlib@sourceware.org Content-Type: multipart/alternative; boundary="000000000000ad586d061bfa653b" X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --000000000000ad586d061bfa653b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks everyone. I guess the broader question with multiple standards being released close to each other, is do we need a master plan? Or just fix things as they are spotted. It seems there are a number of things to address this time. --joel On Fri, Jun 28, 2024 at 4:33=E2=80=AFPM w= rote: > On 2024-06-28 08:37, Joel Sherrill wrote: > > Hi > > > > I am finishing up reviewing the additions from POSIX Issue 8 which was > released > > recently. I noticed a few things and have questions on the right > approach. > > > > + I only have the final draft for POSIX-2024. It says "_POSIX_VERSION to > the value > > 20yymmL." It isn't on the web yet for the HTML version. Anyone know the > value > > this has in the final version? > > The Austin Group minutes say in: > > > https://www.mail-archive.com/austin-group-l@opengroup.org/msg12711.html > > "The IEEE and The Open Group pdf edition was published on Friday June > 14th." > > so I would expect POSIX-1.2004/IEEE Std. 1003-1(2024) to have 202406L dat= e. > > Another email states it could take another month for the HTML ~July 21. > > > + sys/features.h appears to need this new POSIX version added at least > to the > > comment block. I don't think it necessarily changes any logic below tha= t. > > The latest draft normative references include ISO/IEC 10646:2020 (6th > edition) > so Unicode should be at least 13 dated 2020-03-06 and __STDC_ISO_10646__ > at > least 202003L. > This was amended by ISO/IEC 10646:2020/Amd1:2023 2023-07-17 so Unicode > could be > up to 15.0 dated 2022-09-09 with __STDC_ISO_10646__ 202209L. > There were no amendments for Unicode 14 2021-09-10 or 15.1 2023-08-28. > Future considerations expect Unicode 16 in Amendment 2:2025. > > ISO/IEC JTC 1/SC2 WG2 is no longer at http://std.dkuug.dk/jtc1/sc2/wg2 > (NXDOMAIN) so old working documents are no longer available but has moved > to > https://www.unicode.org/wg2/ where more recent working documents are > available, > and hopes are that ISO/IEC standards can be stabilized with normative > references > to Unicode specs like UTS Unicode Technical Standards and UAX Unicode > Standard > Annexes. > > > + memmem is in string.h under the __GNU_VISIBLE guard. Does it now need > to be > > under a __POSIX_VISIBLE > 2024mmdd and __GNU_VISIBLE? > > > > + aligned_alloc in stdlib.h is only guarded by C > 2011. Does that need > to be an > > || POSIX >=3D 2024 also? > > > > + C11 and POSIX-2024 add these complex methods. > > > > double complex CMPLX(double x, double y); > > float complex CMPLXF(float x, float y); > > long double complex CMPLXL(long double x, long double y); > > > > FreeBSD has a macro implementation > > (https://github.com/lattera/freebsd/blob/master/include/complex.h#L49 > > ). > If I > > add that to complex.h, does it also need a __ISO_C_VISIBLE >=3D 2011 || > > __POSIX_VISIBLE > 2024mmdd guard? > > The same minutes linked above says: > > "The ISO/IEC [POSIX] ballot closes on June 28." > > Also note that ISO/IEC 9899:2024 C is targeted for July 12, and JTC 1/SC > 22/WG > 14 hope to get that passed by some picky ISO editors in time, or it will > be > cancelled for this year. > > So look for ISO C >=3D 2024 and add changes, including docs and compiler > options, > and note 202X is becoming ambiguous so groups are using 202Y. > > > + Should I continue to look for guards on things that are newly added in > POSIX > > 2024 and already in newlib? > > > > That's it so far. Just picky stuff that I plan to address given some > advice. > > I am also waiting to see if this will be issued as SUSv5? > > -- > Take care. Thanks, Brian Inglis Calgary, Alberta, Canada > > La perfection est atteinte Perfection is achieved > non pas lorsqu'il n'y a plus rien =C3=A0 ajouter not when there is no mo= re to > add > mais lorsqu'il n'y a plus rien =C3=A0 retirer but when there is no mo= re to > cut > -- Antoine de Saint-Exup=C3=A9ry > --000000000000ad586d061bfa653b--