From: Robin Murphy <robin.murphy@arm.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Naohiro Aota <naohiro.aota@wdc.com>,
Stephen Boyd <swboyd@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Manoj Gupta <manojgupta@google.com>,
Luis Lozano <llozano@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: vdso32: force vdso32 to be compiled as -marm
Date: Wed, 27 May 2020 20:28:12 +0100 [thread overview]
Message-ID: <34f261f7-c4b5-a628-9a4c-eb97b75fba52@arm.com> (raw)
In-Reply-To: <CAKwvOd=Oy_OfRbL6-q-3CAHxWBNBKE+HkfNfgCiP726u+4dU1Q@mail.gmail.com>
On 2020-05-27 18:55, Nick Desaulniers wrote:
> On Wed, May 27, 2020 at 6:45 AM Robin Murphy <robin.murphy@arm.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?
It can be, if you choose to build with frame pointers and the common
frame pointer ABI for Thumb code that uses r7. However it can also be
for other things like the syscall number in the Arm syscall ABI too. I
take it Clang has decided that writing syscall wrappers with minimal
inline asm is not a thing people deserve to do without arbitrary other
restrictions?
> What is the implicit default of your gcc-arm-linux-gnueabihf at -O2?
> -mthumb, or -marm?
As Dave pointed out, like the probable majority of users it's Thumb:
$ arm-linux-gnueabihf-gcc -v
Using built-in specs.
COLLECT_GCC=arm-linux-gnueabihf-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/arm-linux-gnueabihf/8/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
8.3.0-6ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8 --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libitm --disable-libquadmath --disable-libquadmath-support
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --enable-multiarch --enable-multilib
--disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16
--with-float=hard --with-mode=thumb --disable-werror --enable-multilib
--enable-checking=release --build=aarch64-linux-gnu
--host=aarch64-linux-gnu --target=arm-linux-gnueabihf
--program-prefix=arm-linux-gnueabihf-
--includedir=/usr/arm-linux-gnueabihf/include
Thread model: posix
gcc version 8.3.0 (Ubuntu/Linaro 8.3.0-6ubuntu1)
(yeah, I didn't actually need to hack my makefile at all)
Robin.
next prev parent reply other threads:[~2020-05-27 19:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:31 Nick Desaulniers
2020-05-26 18:55 ` Stephen Boyd
2020-05-26 20:45 ` Will Deacon
2020-05-27 13:53 ` Dave Martin
2020-05-27 17:58 ` Nick Desaulniers
2020-05-27 13:45 ` Robin Murphy
2020-05-27 17:55 ` Nick Desaulniers
2020-05-27 18:08 ` Will Deacon
2020-05-27 18:17 ` Nick Desaulniers
2020-05-28 7:20 ` Will Deacon
2020-06-08 20:57 ` [PATCH v2] arm64: vdso32: add CONFIG_THUMB2_COMPAT_VDSO Nick Desaulniers
2020-06-09 20:35 ` Catalin Marinas
2020-06-09 23:55 ` Nick Desaulniers
2020-06-10 8:47 ` Will Deacon
2020-06-10 10:29 ` Catalin Marinas
2020-06-10 10:32 ` Will Deacon
2020-06-10 11:21 ` Will Deacon
2020-05-27 19:28 ` Robin Murphy [this message]
2020-05-27 20:02 ` [PATCH] arm64: vdso32: force vdso32 to be compiled as -marm Robin Murphy
2020-05-27 20:14 ` Nick Desaulniers
2020-05-27 20:31 ` Nick Desaulniers
2020-05-27 21:47 ` Nick Desaulniers
2020-05-28 8:05 ` Peter Smith
2020-05-28 9:41 ` Catalin Marinas
2020-05-28 19:06 ` Nick Desaulniers
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=34f261f7-c4b5-a628-9a4c-eb97b75fba52@arm.com \
--to=robin.murphy@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llozano@google.com \
--cc=manojgupta@google.com \
--cc=masahiroy@kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=swboyd@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®