A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1949 ====================================================================== Reported By: alx Assigned To: ====================================================================== Project: 1003.1(2024)/Issue8 Issue ID: 1949 Category: System Interfaces Type: Enhancement Request Severity: Objection Priority: high Status: New Name: Alejandro Colomar Organization: Linux man-pages project User Reference: Section: realloc, posix_memalign, aligned_alloc, malloc, calloc Page Number: I don't know. Line Number: I don't know. Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2025-09-21 12:31 UTC Last Modified: 2025-10-09 21:43 UTC ====================================================================== Summary: Restore the traditional realloc(3) specification ======================================================================
---------------------------------------------------------------------- (0007288) alx (reporter) - 2025-10-09 21:43 https://www.austingroupbugs.net/view.php?id=1949#c7288 ---------------------------------------------------------------------- > The Austin Group discussed this on 9 Oct 2025, and is in general in favor of tightening the requirements on allocations of size 0 for Issue 9, to eliminate EINVAL for an unsupported size 0. Thanks! > However, as Issue 9 will likely depend on C2Y, we would prefer to delay wordsmithing and determination of which portions of the text may still need <CX> shading until after C2Y has settled on their parallel project of improving the specifications of allocation behavior on a size of 0. I'll tell this to the C committee. Hopefully, they'll read the proposal this time... I'll come back here with whatever they do. I suggest that if the C committee doesn't accept this in the next meeting, POSIX takes the first step. There's still part of the committee that prefers to leave this API broken, which is bad for all. Cheers, Alex Issue History Date Modified Username Field Change ====================================================================== 2025-09-21 12:31 alx New Issue 2025-09-21 12:32 alx Note Added: 0007273 2025-09-21 16:04 dalias Note Added: 0007274 2025-10-09 15:22 agadmin Description Updated 2025-10-09 15:22 agadmin Interp Status => --- 2025-10-09 15:46 eblake Note Added: 0007286 2025-10-09 21:43 alx Note Added: 0007288 ======================================================================
