https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118853
Pavel M <pavel.morozkin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pavel.morozkin at gmail dot com
--- Comment #4 from Pavel M <pavel.morozkin at gmail dot com> ---
FYI: originally the issue was discovered on Clang
(https://github.com/llvm/llvm-project/issues/63403), which probably "just
follows GCC".
(In reply to Zack Weinberg from comment #0)
> "-fmax-errors=2" could be understood to mean "halt processing if _more than_
> two errors are encountered"
(In reply to Richard Biener from comment #3)
> -fstop-after-error=N might have been the better option name
Adapting the text from the link above to GCC:
> Why the triggering condition for -fmax-errors=N is "exceeded" rather than
> "reached"? Should it be "reached"? Will it be useful to implement "reached"
> (perhaps as -ferror-limit-reached)?
I doubt whether changing behavior of -fmax-errors=N may break end user existing
scenarios (e.g. GCC is called by shell scripts, etc.).
To Zack Weinberg: thanks for your time writing and filing this bug report.
