is it possible to force gcc to report errors, but keep compiling past them? Essentially I'm trying to generate a list of errors in a .c file, but gcc always terminates at the first error. I've been googling for a while and this isn't an obvious one to solve from what I can tell.
相关问题
- Is shmid returned by shmget() unique across proces
- how to get running process information in java?
- (ASP.NET) Project file must include 'WindowsBa
- Error building gcc 4.8.3 from source: libstdc++.so
- Why should we check WIFEXITED after wait in order
GCC terminates when it can't go further.
If a compiler encounters an error, it has to guess what the correct code should be and try to follow. Effectively that means that you always need to fix the first error and re-run the compilations, since the rest will be nonsense.
Make sure that you haven't turned
-Wfatal-errors
on.Up-to-date versions of GCC will attempt to skip certain errors where possible.
Say the body of
foo(){...
contains a const-violation. The translation unit will not produce an object file but any decent compiler will continue past this error intobar(){...
Other errors are unrecoverable. If you miss out some curly braces there's no reasonable guess that can be mades as to how to proceed.
From gcc online doc: