https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97424
--- Comment #6 from Florian Weimer <fw at gcc dot gnu.org> --- (In reply to David Malcolm from comment #5) > The above commit implements it as an analyzer warning. Should I close this > out, or should we keep it open for the __builtin_warning approach? Thanks for the analyzer warning. I think the __builtin_warning approach is very desirable here. To me, it looks like GCC already did all the work to figure out this undefined.
