Richard pointed out that plain arm-elf-gcc uses more stack than rowley, which in turn uses more than iar. so i’m looking at ways to reduce the stack size used with gcc and optimize it as far as possible.
- do you have any suggestion about what configuration parameters or other ways might tuning arm-elf-gcc? (and how does rowley do it, if it’s based on gcc?)
- do i understand it right that the amount of stack size eaten up (i’m not talking about the amount allocated) depends on the compiled code in a way that the optimization is to be searched for in the compiling stage, not at the linking stage?
- last time i used iar was a while ago with msp430 , and it seemed to be 100% gui-bound. is there also a command-line compiler included?
- is it practically feasible to link together stuff compiled separately with iar and gcc?
- as it’s openly available for a multitude of host OSes (including linux) and target architectures and since i feel at home with gcc, make etc (and like the way it’s all open), i have pretty much standardized all i could on gcc and feel reluctant about changing to a proprietary compiler suite. right now, apart from the bigger stack size (which isn’t so problematic), i’m quite happy with gcc. I 'm still a little fresh with arm and FreeRTOS though, so is there any other problem about arm-elf-gcc that i should know about?
- any other ideas or comments related to optimizations of gcc or how to get them to work together?