public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	Antonio Terceiro <antonio.terceiro@linaro.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Matthias Klose <doko@debian.org>,
	stable@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: drop cc-option fallbacks for architecture selection
Date: Mon, 18 Oct 2021 21:10:58 +0200	[thread overview]
Message-ID: <20211018191058.3zn5l7ocgh2twy5d@flow> (raw)
In-Reply-To: <20211018140735.3714254-1-arnd@kernel.org>

On 2021-10-18 16:07:12 [+0200], Arnd Bergmann wrote:
…
> Passing e.g. -march=armv6k+fp in place of -march=armv6k would avoid this
> issue, but the fallback logic is already broken because all supported
> compilers (gcc-5 and higher) are much more recent than these options,
> and building with -march=armv5t as a fallback no longer works.
> 
> The best way forward that I see is to just remove all the checks, which
> also has the nice side-effect of slightly improving the startup time for
> 'make'.
> 
> This should be safe to apply on all stable kernels, and will be required
> in order to keep building them with gcc-11 and higher.

Yes, please.

> Reported-by: Antonio Terceiro <antonio.terceiro@linaro.org>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Reported-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
> Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996419
> Cc: Matthias Klose <doko@debian.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>

Just booted Debian 9/ Stretch which ships
   gcc version 6.3.0 20170516 (Debian 6.3.0-18) 

to confirm that it fails to compile with the armv5t fallback.

Sebastian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-18 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 14:07 [PATCH] ARM: drop cc-option fallbacks for architecture selection Arnd Bergmann
2021-10-18 19:10 ` Sebastian Andrzej Siewior [this message]
2021-11-03 20:27 ` Klaus Kudielka
2021-11-05  8:12 ` Sebastian Andrzej Siewior
2021-11-06 16:59 ` Sebastian Reichel
2021-11-06 19:04   ` Arnd Bergmann
2021-11-09 21:26     ` Salvatore Bonaccorso

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=20211018191058.3zn5l7ocgh2twy5d@flow \
    --to=sebastian@breakpoint.cc \
    --cc=antonio.terceiro@linaro.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=doko@debian.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=masahiroy@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=stable@vger.kernel.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