diff options
| author | Pirama Arumuga Nainar <pirama@google.com> | 2015-07-09 12:37:19 -0700 |
|---|---|---|
| committer | Steve Kondik <steve@cyngn.com> | 2015-10-31 14:41:26 -0700 |
| commit | 2a3745d065e4e1cfd2940acfe1ae75f61244c27c (patch) | |
| tree | 22985827a3d3f8536275deeb8fb4bed9e4dbd7eb /core/prebuilt.mk | |
| parent | 23624be825c9493265607e3a8216e46319790371 (diff) | |
| download | build-2a3745d065e4e1cfd2940acfe1ae75f61244c27c.zip build-2a3745d065e4e1cfd2940acfe1ae75f61244c27c.tar.gz build-2a3745d065e4e1cfd2940acfe1ae75f61244c27c.tar.bz2 | |
Add -mfpu=neon-vfpv4 if cpu is krait
Upstream clang r239152 (http://reviews.llvm.org/D10239) caused a pretty
significant change in behavior. Passing an FPU feature via -mfpu
disables any feature not supported by those flags (in addition to the
old behavior of enabling features supported by the flags). For e.g.,
-mfpu=neon used to just pass +neon, +vfp3 as target features to the
backend. Now, -mfpu=neon also passes -vfp4, -fp16, -fp-armv8.
The backend has always disabled implied feature bits if a feature is
disabled. Upon seeing the target feature -vfp4, it will disable any
processor/feature that implies vfp4, including the bit that the
processor is a Krait. Since Krait has both Neon and vfp4, it is safe to
pass '-mfpu=neon-vfpv4'.
Change-Id: Ibbb992e80b8cbc8dc36d5df556885d0912baea22
Diffstat (limited to 'core/prebuilt.mk')
0 files changed, 0 insertions, 0 deletions