You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hashable-1.4.5.0 has been released recently and has already been included in the last hackage.nix and stackage nightly revision. This package now vendors xxhash and includes a package flag arch-native to pass -march=native to C compiler to harvest SIMD speedup. And arch-native defaults to True, which will cause the nix build artifacts to silently depend on CPU models of the nix builders, causing potential run-time crash on machines with older CPU models and breaking nix build purity silently.
I believe haskell.nix has hackage-quirks.nix that enables overriding default package flags for hackage packages, and arch-native: False should be enforced for hashable >= 1.4.5.0.
This might be a non-issue, see NixOS/nixpkgs#318321 (comment), feel free to close this one, though it would be better if someone familiar with nixpkgs internal to actually confirm.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
hashable-1.4.5.0
has been released recently and has already been included in the lasthackage.nix
and stackage nightly revision. This package now vendorsxxhash
and includes a package flagarch-native
to pass-march=native
to C compiler to harvest SIMD speedup. Andarch-native
defaults toTrue
, which will cause the nix build artifacts to silently depend on CPU models of the nix builders, causing potential run-time crash on machines with older CPU models and breaking nix build purity silently.I believe
haskell.nix
hashackage-quirks.nix
that enables overriding default package flags for hackage packages, andarch-native: False
should be enforced forhashable >= 1.4.5.0
.Related upstream issue (closed by maintainer): haskell-unordered-containers/hashable#308
The text was updated successfully, but these errors were encountered: