... | ... | @@ -32,35 +32,10 @@ This messages are present in both debug builds and release builds of the compile |
|
|
|
|
|
The logging follows different levels of verbosity.
|
|
|
The caller sets the verbosity levels by using the `-v` flag.
|
|
|
This info is from the top of the `ctinfo.c` file:
|
|
|
|
|
|
```
|
|
|
* Verbose level 0:
|
|
|
*
|
|
|
* Only error messages are printed.
|
|
|
*
|
|
|
* Verbose level 1:
|
|
|
*
|
|
|
* Error messages and warnings are printed.
|
|
|
*
|
|
|
* Verbose level 2:
|
|
|
*
|
|
|
* Error messages, warnings and basic compile time information, e.g. compiler
|
|
|
* phases, are printed.
|
|
|
*
|
|
|
* Verbose level 3:
|
|
|
*
|
|
|
* Error messages, warnings and full compile time information are printed.
|
|
|
*
|
|
|
* Verbose level 4+:
|
|
|
*
|
|
|
* Additional compile time information is provided that typically is only
|
|
|
* of interest in certain situation.
|
|
|
*
|
|
|
* Default values are 1 for the product version and 3 for the developer version.
|
|
|
```
|
|
|
|
|
|
However `ctinfo.c` holds more logging functions like `InternalCompilerErrorBreak` which produces the `OOOOOOOPS, your program crashed the compiler 8-((` message.
|
|
|
Or for instance `CTIerror` which is used to print an error messages or `CTIwarn` to show warnings etc.
|
|
|
|
|
|
See [ctinfo-messaging](./ctinfo-messaging.md) for more information on how to use these functions.
|
|
|
|
|
|
|