From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: Aarch64 kernel with 32bit userspace question
Date: Thu, 9 Feb 2017 18:29:15 +0800 [thread overview]
Message-ID: <20170209182915.6d909f3f@xhacker> (raw)
In-Reply-To: <0057242a-2e16-3b59-1f81-9f4ccf64216d@denx.de>
On Thu, 9 Feb 2017 11:14:19 +0100
Marek Vasut <marex@denx.de> wrote:
> Hi,
>
> I'm trying multilib userland on aarch64, but I'm running into a problem.
> I have a simple test code:
>
> -->8--
> #include <signal.h>
>
> int main(void) {
> return 0;
> }
> --8<--
>
> If I compile that with aarch64 gcc , it compiles just fine.
>
> If I compile the same thing with 32bit armv7ahf multilib gcc, the
> build fails on "unknown type name '__uint128_t'". This comes from
> arch/arm64/include/uapi/asm/sigcontext.h , which has __uint128_t in
> struct fpsimd_context {} . The signal.h includes that (through a few
> glibc headers) and that's what triggers the failure. __uint128_t is
> defined on aarch64 , but it is not on armv7a (32bit).
>
which 32bit toolchain are you using?
I didn't see any problems with 32bit armhf linaro toolchain, or the
toolchain in debian armhf or ubuntu
next prev parent reply other threads:[~2017-02-09 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 10:14 Aarch64 kernel with 32bit userspace question Marek Vasut
2017-02-09 10:29 ` Jisheng Zhang [this message]
2017-02-09 10:43 ` Marek Vasut
2017-02-09 10:46 ` Jisheng Zhang
2017-02-09 10:51 ` Ard Biesheuvel
2017-02-09 11:14 ` Marek Vasut
2017-02-09 11:24 ` Ard Biesheuvel
2017-02-09 12:25 ` Russell King - ARM Linux
2017-02-09 20:38 ` Marek Vasut
2017-02-10 12:39 ` Arnd Bergmann
2017-02-18 22:20 ` Marek Vasut
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=20170209182915.6d909f3f@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).