https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117867
Bug ID: 117867
Summary: -Wfatal-errors vs -fmax-errors=1 inconsistency
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
Target Milestone: ---
Using my example from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117866#c0, I
see:
```
$ gcc paths.i -fmax-errors=1 -Wall -Wextra
paths.c: In function ‘t1_Loc’:
paths.c:219:22: error: passing argument 1 of ‘S->convert’ from incompatible
pointer type [-Wincompatible-pointer-types]
219 | r->context = S->context;
| ^~~~~~~~
| |
| struct fractpoint *
paths.c:219:22: note: expected ‘struct fractpoint *’ but argument is of type
‘struct fractpoint *’
compilation terminated due to -fmax-errors=1.
```
vs
```
$ gcc paths.i -Wfatal-errors -Wall -Wextra
paths.c: In function ‘t1_Loc’:
paths.c:219:22: error: passing argument 1 of ‘S->convert’ from incompatible
pointer type [-Wincompatible-pointer-types]
219 | r->context = S->context;
| ^~~~~~~~
| |
| struct fractpoint *
compilation terminated due to -Wfatal-errors.
```
i.e. for -Wfatal-errors, we don't get the note.
