https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #9 from CVS Commits ---
The master branch has been updated by Qing Zhao :
https://gcc.gnu.org/g:070a6bf0bdc6761ad77ac97404c98f00a7007d54
commit r14-2197-g070a6bf0bdc6761ad77ac97404c98f00a7007d54
Author: Qing Zhao
Date: Thu Jun 29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #8 from qinzhao at gcc dot gnu.org ---
for record purpose, the code in glibc has already been fixed.
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611220.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #7 from qinzhao at gcc dot gnu.org ---
the patch for this documentation change in GCC has been posted and approved
at:https://gcc.gnu.org/pipermail/gcc-patches/2023-May/620148.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
Siddhesh Poyarekar changed:
What|Removed |Added
CC||siddhesh at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #5 from Martin Sebor ---
Documenting the semantics of this extension would work, though to be usable
safely, GCC would also need to change to recognize that the nested flexible
array member aliases the subsequent members and treat the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #4 from Richard Biener ---
So maybe document this as an extension (and specify its semantics -- I'm
curious how the glibc code behaves)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #3 from joseph at codesourcery dot com ---
Anything based on whether things are in system headers won't work for
building glibc as the headers don't look like system headers when building
glibc (which uses -Wall -Werror).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #2 from Martin Sebor ---
Thanks for the background. It's unfortunate but I hope the Glibc code can be
accommodated without preventing GCC from detecting the same problem in user
code (and rejecting it with a hard error). One approac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #1 from joseph at codesourcery dot com ---
On Mon, 19 Sep 2016, msebor at gcc dot gnu.org wrote:
> While testing my patch for C++ bug 71912 and gathering material for WG14 paper
> N2083 I noticed that GCC isn't completely consistent
