optimizationgccembeddedmemory-footprintgreenhills

GCC vs Greenhills on ARM


I'm interested in any comparisons between GCC and Greenhills C compiler with regard to memory footprint of generated code specifically on ARM platforms.

Are there any benchmarks or comparisons for these compilers? Has anyone had any experience here that they'd like to share?


Solution

  • I have not seen any benchmarks but from my experience the two compilers is very similar code size and the code generated.

    Green Hills has lots of documentation and support if you want to reduce your memory foot print, with GCC it get lonely very fast once your off the beaten track. Green Hills also support compressed executable images that is great if you have limited FLASH but plenty RAM.

    I have also used custom runtime and C libraries (This can save you some more space) with both compilers but you will need to do some digging to get info for GCC but the Green hills you can get some of the stuff via a wizard that generates the build file.