Arm None Linux Gnueabi Gcc Windows Code And Build

The only thing that came to my mind is, that libraries maybe have to be statically linked (do they) while compiling bare metal software, because there is no os dynamically providing them.

Im a student of mechatronics and new to embedded systems, so my experience in this field is somewhat limited.

For bare metal work, either is fine as they can both make assembly from C and make objects from assembly and link with your own linker scripts, etc.

And the bare metal i am talking about is one without standard libraries andor you use this tool to create your own libraries from sources.

Basically they both work as generic cross compilers, if you wantneed built in library support, then it may matter which one you use.

For one, iirc, arm-none- is a freestanding implementation by default, so it does not rely on the C stdlib for hosted systems and gcc does not use its built-in optimisations for certain standard library functions.

Arm None Linux Gnueabi Gcc Windows Code And Build

It is very dependent though on the user and their code and build system.

And yes the gcc lib things can very quickly get system dependent so I control those as well.

Therefore, the compiler may make different function calls depending on what it believes is available above and beyond the Standard C library.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged linux embedded abi toolchain or ask your own question.