From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] kernel mode NEON support
Date: Sun, 22 Sep 2013 11:11:55 +0100 [thread overview]
Message-ID: <20130922101155.GP12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1373321521-15485-1-git-send-email-ard.biesheuvel@linaro.org>
On Mon, Jul 08, 2013 at 11:11:56PM +0100, Ard Biesheuvel wrote:
> This is version 3 of the kernel mode NEON patch set.
I've noticed some of the randconfigs are failing due to trying to mix
VFP and FPA objects together, which causes the linker to complain.
I thought about adding -Wa,-mfpu=softvfp, but this overrides your
-mfpu=neon resulting in the neon code failing to build. -mfpu=softvfp
doesn't work because GCC and binutils don't take the same -mfpu=
option names (GCC rejects softvfp, whereas the assembler accepts it.)
This only happens when AEABI is not selected, so I think the only
solution to this is to make KERNEL_MODE_NEON depend on AEABI - and
this is what I've committed to my tree today.
next prev parent reply other threads:[~2013-09-22 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 22:11 [PATCH v3 0/5] kernel mode NEON support Ard Biesheuvel
2013-07-08 22:11 ` [PATCH v3 1/5] ARM: move VFP init to an earlier boot stage Ard Biesheuvel
2013-07-08 22:11 ` [PATCH v3 2/5] ARM: be strict about FP exceptions in kernel mode Ard Biesheuvel
2013-07-08 22:11 ` [PATCH v3 3/5] ARM: add support for kernel mode NEON Ard Biesheuvel
2013-07-08 22:12 ` [PATCH v3 4/5] ARM: crypto: add NEON accelerated XOR implementation Ard Biesheuvel
2013-07-08 22:12 ` [PATCH v3 5/5] lib/raid6: add ARM-NEON accelerated syndrome calculation Ard Biesheuvel
2013-07-08 22:16 ` H. Peter Anvin
2013-09-22 10:11 ` Russell King - ARM Linux [this message]
2013-09-22 10:24 ` [PATCH v3 0/5] kernel mode NEON support Ard Biesheuvel
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=20130922101155.GP12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.