This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why is GCC9.2-2019.12 arm-none-linux-gnueabihf configured without "--with-fpu=vfpv3-d16"?

Dear ARM A GNU Toolchain maintainers,

I have noticed that the latest AArch32 Linux GCC release v9.2-2019.12 for ARM A is configured without a default fpu option whereas ARM GCC v8.3-2019.03 and older Linaro toolchains used "--with-fpu=vfpv3-d16". The example ABE manifest file for v9.2 also still contains this option. Could you please explain the background for this configuration change?

Thank you very much,

Andrej

Parents
  • Thank you very much, no idea how I could overlook the neon setting.

    Just for the understanding: there are 4 sets of gcc configure sets (gcc{1,2,3,4}_configure) in the manifest you pointed me at in contrast to ABE's stage1/stage2. What is the difference in ARM's approach there?

    EDIT: the manifest file lacks glibc configuration information. Do you have a hint where to find it?

    Kind regards

    Andrej

Reply
  • Thank you very much, no idea how I could overlook the neon setting.

    Just for the understanding: there are 4 sets of gcc configure sets (gcc{1,2,3,4}_configure) in the manifest you pointed me at in contrast to ABE's stage1/stage2. What is the difference in ARM's approach there?

    EDIT: the manifest file lacks glibc configuration information. Do you have a hint where to find it?

    Kind regards

    Andrej

Children