Skip to content

targetByteOrder on s390x

Summary

I suspect that GHC detects the wrong byte order for s390x. This was originally reported against the byte-order library, but it actually appears to be a problem with GHC itself that manifests itself as a failure in byte-order's test suite.

Steps to reproduce

On an s390x host, run this in GHCi:

$ ghci
GHCi, version 8.8.3: https://www.haskell.org/ghc/  :? for help
Prelude> import qualified GHC.ByteOrder
Prelude GHC.ByteOrder> GHC.ByteOrder.targetByteOrder
LittleEndian

Expected behavior

This is a big-endian architecture. The result should be BigEndian.

Environment

  • GHC version used: Not yet certain. I do not have access to the machine that fails.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information