SUSE Package Hub 15 one-click install Install ghc-fast-math NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-Standard-Pool Package Hub 15 Dummy repo - this will fail ghc-fast-math Non IEEE-754 compliant compile-time floating-point optimisations The "Numeric.FastMath" module brings into scope many unsafe 'RULES' for 'Float's and 'Double's that can greatly improve run time performance. It is roughly equivalent to gcc's '-ffast-math' compiler flag. Optimisation (at least '-O1') must be enabled for any 'RULES' to take effect. These rules are unsafe because they don't strictly adhere to the IEEE-754 regulations and may subtly change the results of your numeric computations. See the <http://github.com/liyang/fast-math/ README> on github for more details. SUSE Package Hub 15 one-click install Install ghc-fast-math NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-Standard-Pool Package Hub 15 Dummy repo - this will fail ghc-fast-math Non IEEE-754 compliant compile-time floating-point optimisations The "Numeric.FastMath" module brings into scope many unsafe 'RULES' for 'Float's and 'Double's that can greatly improve run time performance. It is roughly equivalent to gcc's '-ffast-math' compiler flag. Optimisation (at least '-O1') must be enabled for any 'RULES' to take effect. These rules are unsafe because they don't strictly adhere to the IEEE-754 regulations and may subtly change the results of your numeric computations. See the <http://github.com/liyang/fast-math/ README> on github for more details.