https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66528
Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 Status|UNCONFIRMED |NEW Known to work| |5.1.0 Keywords| |error-recovery Last reconfirmed| |2015-06-13 CC| |pault at gcc dot gnu.org Ever confirmed|0 |1 Summary|unbalanced IF/ENDIF with |[6 Regression] unbalanced |-fmax-errors=1 causes |IF/ENDIF with |invalid free |-fmax-errors=1 causes | |invalid free Known to fail| |6.0 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > Much better with a test case, of course. Indeed!-) Revision r223447 (2015-05-20) gives Error: END IF statement expected at (1) compilation terminated due to -fmax-errors=1. Revision r223694 (2015-05-26) gives compilation terminated due to -fmax-errors=1. f951(2326,0x7fff7bef0300) malloc: *** error for object 0x1412fd9a8: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug (null):0: confused by earlier errors, bailing out f951(2326,0x7fff7bef0300) malloc: *** error for object 0x142002200: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Usual suspect r223677 (pr66082).