Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 400
    • Issues 400
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Wiki
  • Tutorials
  • logging

logging · Changes

Page history
Move ctinfo part in logging.md to dedicated file authored Apr 09, 2025 by Quinten Cabo's avatar Quinten Cabo
Show whitespace changes
Inline Side-by-side
tutorials/logging.md
View page @ 8c51b29e
...@@ -32,35 +32,10 @@ This messages are present in both debug builds and release builds of the compile ...@@ -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 logging follows different levels of verbosity.
The caller sets the verbosity levels by using the `-v` flag. 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. 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. 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.
Clone repository
  • Styleguide
  • concepts
    • Deprecated Modules
    • Globals
    • Intermediate Code Macros
    • Named Tuples
    • Overloading
    • Preprocessor
    • Primitive functions
    • Runtime Representations
    • input stdin
    • phm xt
    • ref counting methods
    • type famlies
    • type patterns
  • error messages
    • Anthropomorphic error essages
View All Pages