mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: barebox@lists.infradead.org
Subject: Build failures with CC=arm-linux-gnueabihf-gcc-11
Date: Thu, 18 Nov 2021 15:32:04 +0000	[thread overview]
Message-ID: <62b76c10-a376-a2f5-5b21-fdda86db4a03@mev.co.uk> (raw)

Hi,

My Debian "testing" build system updated the default version of 
arm-linux-gnueabihf-gcc from 10.x to 11.x.  Building barebox in thumb-2 
mode for an ARMv7 (it's a SoCFPGA) with this compiler fails with 
assembler errors such as:

   CC      common/state/state_variables.o
{standard input}: Assembler messages:
{standard input}:1535: Error: selected processor does not support `rev 
r3,r3' in Thumb mode
{standard input}:1576: Error: selected processor does not support `rev 
r3,r3' in Thumb mode

Building in verbose mode (V=1) shows that "make" has selected the 
compile flags `-march=armv5t -Wa,-march=armv7-a` instead of the usual 
`-march=armv7-a`.

Looking a little deeper, all of the following lines in 
"arch/arm/Makefile" are failing to select the first option and 
defaulting to the second option (if any):

arch-$(CONFIG_CPU_64v8)		:= -D__LINUX_ARM_ARCH__=8 $(call 
cc-option,-march=armv8-a)
arch-$(CONFIG_CPU_32v7)		:=-D__LINUX_ARM_ARCH__=7 $(call 
cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
arch-$(CONFIG_CPU_32v6)		:=-D__LINUX_ARM_ARCH__=6 $(call 
cc-option,-march=armv6,-march=armv5t -Wa$(comma)-march=armv6)
arch-$(CONFIG_CPU_32v5)		:=-D__LINUX_ARM_ARCH__=5 $(call 
cc-option,-march=armv5te,-march=armv4t)

The error from the compiler is:

cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

(Note: the error is only shown after tweaking the `try-run` command in 
"scripts/Kbuild.include" so that it does not send error output to 
"/dev/null".)

That error seems to be a change in behaviour between GCC 10.x and GCC 11.x.

At the point in the Makefile that the error occurs, the `-msoft-float` 
option has not been added to `KBUILD_CPPFLAGS` yet. That is done further 
down the Makefile except for `CONFIG_CPU_V8`.  I guess it needs to be 
added somewhere before problematic lines in the Makefile.  I'm not sure 
if `-msoft-float` is also needed for 64-bit ARMv8, but the error 
suggests it is required there too.

-- 
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company  )=-
-=( registered in England & Wales.  Regd. number: 02862268.  )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2021-11-18 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 15:32 Ian Abbott [this message]
2021-11-19  9:29 ` Michael Olbrich
2021-11-19 10:30   ` Ian Abbott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62b76c10-a376-a2f5-5b21-fdda86db4a03@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox