More C type errors by default for GCC 14

Florian Weimer
Tue May 9 20:57:20 GMT 2023

* Eli Zaretskii via Gcc:

>> Date: Tue, 9 May 2023 21:07:07 +0200
>> From: Jakub Jelinek <>
>> Cc: Jonathan Wakely <>,,
>> On Tue, May 09, 2023 at 10:04:06PM +0300, Eli Zaretskii via Gcc wrote:
>> > People who ignore warnings will use options that disable these new
>> > errors, exactly as they disable warnings.  So we will end up not
>> Some subset of them will surely do that.  But I think most people will just
>> fix the code when they see hard errors, rather than trying to work around
>> them.
> The same logic should work for warnings.  That's why we have warnings,
> no?

People completely miss the warning and go to great lengths to show that
what they are dealing is a compiler bug.  (I tried to elaborate on that
in <>.)  If GCC errors out, that
simply does not happen because there is no object code to examine.


More information about the Gcc mailing list