https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126331
--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> --- But we silently accept this as C, and existing code (including the Linux kernel) has instances of such code, at the same time relying on results from __builtin_object_size for security hardening. If all programs were correct there wouldn't be much need to introduce __builtin_object_size in the first place. Is there any particular reason we yield a wrong size here?
