[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH1P110MB16361EF635C579E30308D647CC85A@PH1P110MB1636.NAMP110.PROD.OUTLOOK.COM>
Date: Thu, 8 Jan 2026 15:20:39 +0000
From: David Svoboda <svoboda@...t.org>
To: Martin Uecker <ma.uecker@...il.com>, Joseph Myers <josmyers@...hat.com>,
Alejandro Colomar <une+c@...jandro-colomar.es>
CC: Robert Seacord <rcseacord@...il.com>, "sc22wg14@...n-std. org"
<sc22wg14@...n-std.org>, Florian Weimer <fweimer@...hat.com>, Carlos O'Donell
<carlos@...hat.com>, Aaron Ballman <aaron@...onballman.com>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>,
"musl@...ts.openwall.com" <musl@...ts.openwall.com>,
"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>, David Svoboda
<svoboda@...t.org>
Subject: Re: [SC22WG14.34679] n3752, alx-0029r8 - Restore the traditional
realloc(3) specification
I would agree. I interpret "informally take over" to mean two things:
1. I would like someone to volunteer to scan the C2y draft standard (n3605) specifically to catch errors in Annex J.2. In particular, are there any UBs in J2 no longer in the standard. Likewise does the standard have any UBs not in J.2? The result would be a document recommending editorial changes to Annex J.2.
2. I would suggest that any documents that add or remove UBs also at least mention that Annex J.2. should be updated. This is a job for all of WG14, not just the Undefined Behavior Study Group (UBSG).
The UBSG has its next meeting tomorrow morning (at 9am EST). I'll make sure this gets on our agenda.
--
David Svoboda svoboda@....cmu.edu<mailto:svoboda@....cmu.edu>
Senior Software Security Engineer
CERT Applied Systems Group
(412) 596-0401
From: Martin Uecker <ma.uecker@...il.com>
Date: Thursday, January 8, 2026 at 9:59 AM
To: Joseph Myers <josmyers@...hat.com>, Alejandro Colomar <une+c@...jandro-colomar.es>
Cc: David Svoboda <svoboda@...t.org>, Robert Seacord <rcseacord@...il.com>, sc22wg14@...n-std. org <sc22wg14@...n-std.org>, Florian Weimer <fweimer@...hat.com>, Carlos O'Donell <carlos@...hat.com>, Aaron Ballman <aaron@...onballman.com>, libc-alpha@...rceware.org <libc-alpha@...rceware.org>, musl@...ts.openwall.com <musl@...ts.openwall.com>, linux-man@...r.kernel.org <linux-man@...r.kernel.org>
Subject: Re: [SC22WG14.34679] n3752, alx-0029r8 - Restore the traditional realloc(3) specification
Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe.
Am Mittwoch, dem 07.01.2026 um 22:01 +0000 schrieb Joseph Myers:
> On Wed, 7 Jan 2026, Alejandro Colomar wrote:
>
> > I thought you were talking about the UB introduced in C23, but that one
> > seems not documented in Annex J. In fact, it's still documented
> > incorrectly as ID (J.3.13 entry 41, in N3220).
>
> See
> https://stackoverflow.com/questions/78691087/reallocptr-0-in-c23-now-what
> regarding the lists of UB related to realloc being out of date. I think
> this could be fixed editorially via a merge request (to make the Annex J
> lists in C2y agree with the actual current realloc semantics in C2y) but I
> haven't got round to writing such an MR myself.
There know of various other issues and omissions in Annex J3. I think
it would be good if the UB study group informally takes over maintenance
of this annex.
Martin
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
