Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: ghc-criterion-measurement | Distribution: openSUSE Leap 16.0 |
Version: 0.2.3.0 | Vendor: openSUSE |
Release: lp160.1.1 | Build date: Sun Oct 27 02:12:23 2024 |
Group: Unspecified | Build host: reproducible |
Size: 479497 | Source RPM: ghc-criterion-measurement-0.2.3.0-lp160.1.1.src.rpm |
Packager: https://bugs.opensuse.org | |
Url: https://hackage.haskell.org/package/criterion-measurement | |
Summary: Criterion measurement functionality and associated types |
Measurement-related functionality extracted from Criterion, with minimal dependencies. The rationale for this is to enable alternative analysis front-ends.
BSD-3-Clause
* Sun Oct 27 2024 Peter Simons <psimons@suse.com> - Update criterion-measurement to version 0.2.3.0. 0.2.3.0 * Drop support for pre-8.0 versions of GHC. * Sun May 12 2024 Peter Simons <psimons@suse.com> - Update criterion-measurement to version 0.2.2.0. 0.2.2.0 * Supporting building with all AArch64 platforms (not just Linux and macOS). * Thu Mar 30 2023 Peter Simons <psimons@suse.com> - Updated spec file to conform with ghc-rpm-macros-2.5.2. * Fri Feb 17 2023 Peter Simons <psimons@suse.com> - Update criterion-measurement to version 0.2.1.0. 0.2.1.0 * Make the behavior of the benchmarking functions independent of the `-fspec-const-count` limit. * Thu Aug 11 2022 Peter Simons <psimons@suse.com> - Update criterion-measurement to version 0.2.0.0. 0.2.0.0 * Add a `measPeakMbAllocated` field to `Measured` for reporting maximum megabytes allocated. Naturally, this affects the behavior of `Measured`'s `{To,From}JSON` and `Binary` instances. * Thu Aug 04 2022 Peter Simons <psimons@suse.com> - Update criterion-measurement to version 0.1.4.0. 0.1.4.0 * Fix a bug that occurred with GHC 9.2.4 or later that would cause incorrect measurements. * Sat Jul 10 2021 psimons@suse.com - Update criterion-measurement to version 0.1.3.0. 0.1.3.0 * Change `criterion_rdtsc` to return `mach_absolute_time` on macOS. This is a portable way of returning the number of CPU cycles that works on both Intel- and ARM-based Macs. * Change `criterion_gettime` to use `clock_gettime_nsec_np` instead of `mach_absolute_time` on macOS. While `mach_absolute_time` has nanosecond resolution on Intel-based Macs, this is not the case on ARM-based Macs, so the previous `mach_absolute_time`-based implementation would return incorrect timing results on Apple silicon. There are two minor consequences of this change: * `criterion-measurement` now only supports macOS 10.02 or later, as that is the first version to have `clock_gettime_nsec_np`. As macOS 10.02 was released in 2002, this is unlikely to affect users, but please speak up if this is a problem for you. * As `clock_gettime_nsec_np` does not require any special initialization code, `criterion_inittime` is now a no-op on macOS. If you manually invoke the `getTime` function in your code, however, it is still important that you `initializeTime` beforehand, as this is still required for the Windows implementation to work correctly. * Mon Apr 26 2021 psimons@suse.com - Add criterion-measurement at version 0.1.2.0.
/usr/lib64/ghc-9.8.3/lib/libHScriterion-measurement-0.2.3.0-KTsJkUUx78fLpGzaFgSXo8-ghc9.8.3.so /usr/share/licenses/ghc-criterion-measurement /usr/share/licenses/ghc-criterion-measurement/LICENSE
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Nov 12 00:13:41 2024