If you need to do run-time stack checking, you will have to implement this yourself. A simple way to check the linker calculation result versus the actual stack usage during run-time is filling the stack area with a specific pattern (like 0xA5A5A5A5 checker/chessboard pattern) and then run...
Possible solutions The following are several recommended practices to optimize and reduce the build time of the TASKING compiler project: Use a workstation with a multi-core CPU and a large amount of PC RAM (32 GB+ is beneficial) to take full advantage of concurrent processing capabilities...
System errors such as S900, S903, S911, and S917 indicate an internal problem with the TASKING C compiler. There is a good chance this is caused by an issue with a certain C compiler optimization. Therefore, disabling this optimization might be a possible mitigation. Possible solution To d...
The description of the TASKING C compiler error E208 is generic, as it does not clearly explain what is wrong. Furthermore, the source code line indicated by the error message is not necessarily where the root cause of the error is present. The cause of the error itself is often trivial. B...
Possible solution To detect a stack overflow during run-time, using the C compiler options, you can use Stack overflow check. To add a stack overflow check , you can use the following C compiler option: --runtime (-r) :+/-stack s/S check for stack overflow In the Eclipse IDE, you can enabl...
For the TASKING C compiler, enabling and disabling optimizations for the complete project or one of its modules can have a significant impact on the entire project. With the #pragma optimize instructions you can selectively enable or disable specific optimizations at the source level, and ...
Solution These command line options provide maximum debug information when using GHS Compiler: dual_debug full_debug_info Omoredebug You should not use ignore_debug_references compiler command line option. For more information refer to Missing callstack information when using GHS Compiler ...
The TriCore CPU core versions v1.3.1 up to v1.6.2 (AURIX 2G) include a hardware FPU unit for floating-point calculations. This makes float calculations very efficient because there are dedicated assembly instructions, for example, for floating-point multiplication, division, addition, or s...
The Callstack Window doesn't show current call stack content or the displayed info is incorrect. Possible solutions Compiler optimization The compiler can optimize the code to the extent that the required information being used by the debugger to extract theCall Stackcontextis not availabl...
Variables missing from the structure or two structures in the ELF with the same name but slightly different types are usually caused by compiler excessive code optimization. Possible solution winIDEA offers an option to control the resolution of variable locations from Symbol table. 1. Ope...
This application note provides details on the internal sections that are generated in addition to the normal code and data sections. It walks you through the following compiler-generated internal sections and describes how they can be utilized: Initializers: *.n.ini.* String literals: *.n....
This topic describes what to do if winIDEA Editor window shows inconsistent or no glyph margin (grey strip or column on the left side of the Editor), icons (glyphs, LoC (Line of Code) markers, debug line symbols,...) for debugging of the opened source file thus disabling source-level debug...
You encountered an error message Can not build EVE script! See Progress view for errors when attempting to start the debug session. The error can be triggered when: Any of the files inside the installation folder winIDEA\eve or eveGcc folder are missing or corrupt Any of the device cpp/h f...