[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOd=Oy_OfRbL6-q-3CAHxWBNBKE+HkfNfgCiP726u+4dU1Q@mail.gmail.com>
Date: Wed, 27 May 2020 10:55:24 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Robin Murphy <robin.murphy@....com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Naohiro Aota <naohiro.aota@....com>,
Stephen Boyd <swboyd@...gle.com>,
Masahiro Yamada <masahiroy@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Manoj Gupta <manojgupta@...gle.com>,
Luis Lozano <llozano@...gle.com>,
Nathan Chancellor <natechancellor@...il.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: vdso32: force vdso32 to be compiled as -marm
On Wed, May 27, 2020 at 6:45 AM Robin Murphy <robin.murphy@....com> wrote:
>
> On 2020-05-26 18:31, Nick Desaulniers wrote:
> > Custom toolchains that modify the default target to -mthumb cannot
> > compile the arm64 compat vdso32, as
> > arch/arm64/include/asm/vdso/compat_gettimeofday.h
> > contains assembly that's invalid in -mthumb. Force the use of -marm,
> > always.
>
> FWIW, this seems suspicious - the only assembly instructions I see there
> are SWI(SVC), MRRC, and a MOV, all of which exist in Thumb for the
> -march=armv7a baseline that we set.
>
> On a hunch, I've just bodged "VDSO_CFLAGS += -mthumb" into my tree and
> built a Thumb VDSO quite happily with Ubuntu 19.04's
> gcc-arm-linux-gnueabihf. What was the actual failure you saw?
>From the link in the commit message: `write to reserved register 'R7'`
https://godbolt.org/z/zwr7iZ
IIUC r7 is reserved for the frame pointer in THUMB?
What is the implicit default of your gcc-arm-linux-gnueabihf at -O2?
-mthumb, or -marm?
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists