[Bug 1939379] Re: ARM kernel builds fail with GCC 11

[dann frazier]

Interesting - here's what I see in the boost1.74 log:

    "g++" -x assembler-with-cpp -fPIC -pthread -O3 -finline-functions
-Wno-inline -Wall -g -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2
-DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_DYN_LINK=1 -DBOOST_CONTEXT_SOURCE
-DBOOST_DISABLE_ASSERTS -DNDEBUG -I"." -c -o
"bin.v2/libs/context/build/gcc-11/release/debug-symbols-on/threading-
multi/visibility-hidden/asm/jump_arm_aapcs_elf_gas.o"
"libs/context/src/asm/jump_arm_aapcs_elf_gas.S"

jump_arm_aapcs_elf_gas.S: Assembler messages:
jump_arm_aapcs_elf_gas.S:57: Error: selected processor does not support `vstmia sp,{d8-d15}' in ARM mode
jump_arm_aapcs_elf_gas.S:68: Error: selected processor does not support `vldmia sp,{d8-d15}' in ARM mode

It's not messing with -march, so seems like g++ should default to having
an FPU?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1939379

Title:
  ARM kernel builds fail with GCC 11

Status in gcc-11 package in Ubuntu:
  Confirmed
Status in gcc-defaults package in Ubuntu:
  Invalid

Bug description:
  While this might be a kernel build problem (see LP: #1939308) I wanted
  to raise the issue against the toolchain just so we can make sure it's
  *not* a toolchain bug. Basically the following behavior changed from
  gcc 10:

  $ arm-linux-gnueabihf-gcc-10 -march=armv7-a -c -x c /dev/null ; echo $?
  0

  $ arm-linux-gnueabihf-gcc-11 -march=armv7-a -c -x c /dev/null ; echo $?
  cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
  1

  Presumably the GCC 11 hard-float compiler now enforces the default
  config --with-float=hard?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1939379/+subscriptions