Posted on May 17, 2011 at 13:07You mean GCC, Ride7 is not a compiler...
One of the shortcomings of GCC when it comes to embedded code is its lack of link time optimization. Which means that if you have a library archive, like what the stm32 fwlib is probably is shipped as with Ride, it contains a bunch of object files. When your application uses a function in the library, the entire object file containing that function must be linked into your binary, including all the unused functions.
There are several solutions to this problem.
Split all the library source files into smaller units, ideally with one function per c-file. The GCC C library is organized this way for this very reason.
Combine all the library c-files into one, copy it to your project and comment out all the functions you do not use. Gives much better optimization possibilities than the first method, but it's not really practical.
Pass the ''-combine -fwhole-program'' flags to the compiler. This requires you to specify on the command line all the c-files which will make up the binary. For example
''gcc $(CFLAGS) -Os -combine -fwhole-program $(LDFLAGS) -o your_app.elf your_src/*.c fwlib/*.c''
GCC will then compile, optimize and link your program as a single unit, and consider all functions static so that they will be dropped if unused. The result is much the same as LTO could have produced. Unfortunately it seems that many GCC versions have problems with these flags in combination with some code constructs, which will cause the compiler to crash. But if it works for your code, its the best solution.
