mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Mark Brown <broonie@kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Paul Burton <paul.burton@mips.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Palmer Dabbelt <palmer@sifive.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH] ARM: Kconfig: default to AEABI w/ Clang
Date: Thu, 4 Jul 2019 09:56:13 +0100	[thread overview]
Message-ID: <20190704085613.dhg25m24irfuf3tx@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAK8P3a1Oucpi0smL1poiKJj9Gc=s_6tVirTDkZwA68cuOjvB7g@mail.gmail.com>

On Thu, Jul 04, 2019 at 10:29:35AM +0200, Arnd Bergmann wrote:
> On Thu, Jul 4, 2019 at 10:13 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Tue, Jun 25, 2019 at 11:04 PM Nick Desaulniers <ndesaulniers@google.com> wrote:
> >
> > > Clang produces references to __aeabi_uidivmod and __aeabi_idivmod for
> > > arm-linux-gnueabi and arm-linux-gnueabihf targets incorrectly when AEABI
> > > is not selected (such as when OABI_COMPAT is selected).
> > >
> > > While this means that OABI userspaces wont be able to upgraded to
> > > kernels built with Clang, it means that boards that don't enable AEABI
> > > like s3c2410_defconfig will stop failing to link in KernelCI when built
> > > with Clang.
> > >
> > > Link: https://github.com/ClangBuiltLinux/linux/issues/482
> > > Link: https://groups.google.com/forum/#!msg/clang-built-linux/yydsAAux5hk/GxjqJSW-AQAJ
> > > Suggested-by: Arnd Bergmann <arnd@arndb.de>
> > > Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> >
> > As reflecting the state of things with CLANG it's:
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > But I think we in general need to have some discussion on how to
> > proceed with OABI userspaces.
> >
> > I am well aware of distributions like OpenWrt using EABI even
> > on ARMv4 with "tricks" like this:
> > https://github.com/openwrt/openwrt/blob/master/toolchain/gcc/patches/9.1.0/840-armv4_pass_fix-v4bx_to_ld.patch
> 
> I did not expect that to be necessary in gcc as long as it supports
> building for armv4 (non-t), but I might be missing something here.
> 
> > I have one OABI that I can think of would be nice to live on
> > and it's the RedHat derivative on my Foorbridge NetWinder.
> > OK I wouldn't cry if we have to kill it because it is too hard to
> > keep supporting it, but it has been running the latest kernels
> > all along so if it's not a huge effort I'd be interested in knowing
> > the options.
> 
> But do you see any problems with cross-compiling kernels to
> EABI with CONFIG_OABI_COMPAT for machines like that?

Yes, there are a few ioctls that break.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

      reply	other threads:[~2019-07-04  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 21:04 Nick Desaulniers
2019-07-04  7:24 ` Arnd Bergmann
2019-07-04  8:13 ` Linus Walleij
2019-07-04  8:29   ` Arnd Bergmann
2019-07-04  8:56     ` Russell King - ARM Linux admin [this message]

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=20190704085613.dhg25m24irfuf3tx@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=ndesaulniers@google.com \
    --cc=palmer@sifive.com \
    --cc=paul.burton@mips.com \
    --cc=rppt@linux.ibm.com \
    --cc=yamada.masahiro@socionext.com \
    /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

all inboxes | Powered by JetHome®