https://bugzilla.redhat.com/show_bug.cgi?id=995419
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #14 from Jens Petersen <petersen(a)redhat.com> ---
I suspect a change to ghc like this:
--- a/compiler/main/DriverPipeline.hs
+++ b/compiler/main/DriverPipeline.hs
@@ -1420,7 +1420,7 @@ runPhase (RealPhase LlvmLlc) input_fn dflags
-- does not enable VFP by default. Let's do this manually here
fpOpts = case platformArch (targetPlatform dflags) of
ArchARM ARMv7 ext _ -> if (elem VFPv3 ext)
- then ["-mattr=+v7,+vfp3"]
+ then ["-mattr=+v7,+vfp3,-neon"]
else if (elem VFPv3D16 ext)
then ["-mattr=+v7,+vfp3,+d16"]
else []
would disable neon for all builds. I don't know if llvm
is able to generate runtime detection+code for neon.
How relevant is tegra2 and other SoC's without neon these days?
If I do a scratch build of ghc without neon is someone able
and willing to test it on a system with neon support?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=LP8dJc3XFg&a=cc_unsubscribe