ARM vs GNUARM Toolchains?

Sysprogs forums Forums VisualGDB ARM vs GNUARM Toolchains?

This topic contains 1 reply, has 2 voices, and was last updated by  support 1 year ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #26412


    Other than the different GCC versions available, what is the difference between the ARM and the GNUARM toolchains? Is one preferable over the other? Is one of them legacy/going obsolete?




    We started shipping our own ARM toolchain (arm-eabi) when the official GNUARM toolchain was still relatively buggy and did not work with many SDKs (e.g. some standard library FP functions were chosen incorrectly for some CPU/FPU combinations). Over the years the quality of the official toolchain has improved, so VisualGDB now supports it out-of-the-box.

    Generally, if you are looking for the latest C++ features, we advise using the latest GNUARM toolchain. As soon as you install it and restart Visual Studio, VisualGDB will automatically detect it and will let you create projects with it. If you encounter any issues, please feel free to let us know. As long it could be mitigated on the VisualGDB side, we should be able to fix it.

    If instead you would like to minimize the chance of incompatibilities between the toolchain and BSPs and don’t care about the latest GCC functionality, the arm-eabi toolchain would be you safest bet.

    We are gradually switching to the GNUARM toolchain in our internal BSP tests and once we get enough confidence with it, we will deprecate the arm-eabi toolchain and make the GNUARM toolchain the default choice.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.