GCC, also known as the GNU Compiler Collection, is a free compiler system produced by the GNU Project supporting various programming languages. The Free Software Foundation (FSF) distributes GCC under the GNU Public License (GNU GPL). GCC has been adopted as the standard compiler by most modern Unix-like computer operating system and has also been ported to a wide variety of processor architectures and is available for most embedded platforms.
GCC is used with permission under the GPL Version 3. If GCC is installed with OpenECU,
the license file can be found in the [install path]\tools\gcc\ppc\docs
directory of the OpenECU install. If desired, a copy of the GCC source code can be found
and downloaded from the Pi Innovo website.
Support for GCC is currently in beta and as such, the user may run into issues which can cause an application to fail to build or run correctly on target. Listed below are a set of known issues when building an application using GCC. See Appendix 10, Contact information for details on how to get in contact with OpenECU support if support is needed for using GCC.
GCC is not recommended for production programs at this time.
GCC is an optional component in the OpenECU installation and is installed by default.
Open: Applications built with the GCC compiler do not support the diagnostics feature at this time. Applications using the diagnostics feature will not compile.
Information: compiler warnings when using Simulink look up blocks.
When building a model that uses Simulink look up blocks, the compiler will emit diagnostic messages similar to the following. These can be ignored.
[file-line]: warning: passing argument 2 of '[lookup function]' discards 'volatile' qualifier from pointer target type [enabled by default] [file-line]: note: expected 'const real_T *' but argument is of type 'const volatile real_T *'
Information: GCC only supports non-VLE code. Therefore, the compiled code will be larger. In general, GCC applications will be about 50% bigger than code generated by Diab.
Information: The GNU linker locates data slightly differently than the Diab linker in the final images. RAM and Flash memory utilization may be different for the same application compiled by different compilers.
Open: Applications built with GCC in general exhibit higher CPU loading than applications build with Diab.