Re: [PATCH] Mention WG14 N3322 in manual

Paul Eggert wrote: > > Do you happen to know whether this proposal has already been approved? > > Yes, it was accepted by WG14 last week. See: > > https://sourceware.org/pipermail/libc-alpha/2024-October/160375.html Thanks. I've reported this glibc bug: https://sourceware.org/bugzilla/show_bug.c

Re: [PATCH] Mention WG14 N3322 in manual

On 2024-10-04 13:23, Bruno Haible wrote: Do you happen to know whether this proposal has already been approved? Yes, it was accepted by WG14 last week. See: https://sourceware.org/pipermail/libc-alpha/2024-October/160375.html It's not yet clear how glibc and gcc will deal with it, for library

Re: [PATCH] Mention WG14 N3322 in manual

Paul Eggert wrote: > +A future C standard is planned to require this behavior; see > +``@url{https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3322.pdf, Do you happen to know whether this proposal has already been approved? If yes, I would ask the clang people to change their UBSAN, so that we ca

[PATCH] Mention WG14 N3322 in manual

--- doc/gnulib-readme.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/doc/gnulib-readme.texi b/doc/gnulib-readme.texi index eafb3a0b01..876a495103 100644 --- a/doc/gnulib-readme.texi +++ b/doc/gnulib-readme.texi @@ -547,6 +547,11 @@ hosts. @item Adding zero to a null pointer does n