"Prelude.chr: bad argument:" exception when attempting to build vector with ghc-9.0.1-alpha-1

[mgsloan]

Steps to reproduce

1. Clone my ghc-9 branch of vector

2. Run stack build --stack-yaml=stack-9.yaml

Expected

Builds, or produces some compilation error.

Actual

$ stack build --stack-yaml=stack-9.yaml                                                                  
Stack has not been tested with GHC versions above 8.10, and using 9.0.0.20200925, this may fail                                      
Stack has not been tested with Cabal versions above 3.2, but version 3.4.0.0 was found, this may fail                                
vector> configure (lib)                                                                                                              
Configuring vector-0.13.0.1...                                                                                                       
                                                                                                                                     
Warning: Failed to decode module interface:
         /home/mgsloan/oss/vector/.stack-work/dist/x86_64-linux/Cabal-3.4.0.0/build/Data/Vector/Internal/Check.hi Decoding failure:
         not enough bytes

Warning: Failed to decode module interface:
         /home/mgsloan/oss/vector/.stack-work/dist/x86_64-linux/Cabal-3.4.0.0/build/Data/Vector/Fusion/Util.hi Decoding failure:
         not enough bytes

Warning: Failed to decode module interface:
         /home/mgsloan/oss/vector/.stack-work/dist/x86_64-linux/Cabal-3.4.0.0/build/Data/Vector/Fusion/Stream/Monadic.hi Decoding
         failure: not enough bytes

Warning: Failed to decode module interface:
         /home/mgsloan/oss/vector/.stack-work/dist/x86_64-linux/Cabal-3.4.0.0/build/Data/Vector/Fusion/Bundle/Size.hi Decoding
         failure: not enough bytes
Prelude.chr: bad argument: 809054773

Not sure where to begin looking to diagnose this. I imagine it is related to deserialization. Hopefully one day ghc's callstack situation will get sorted!

Stack version

$ stack --version
Version 2.6.0, Git revision 4c38ee0125f705cc007109f612b7423342911808 (8258 commits) PRE-RELEASE x86_64 hpack-0.33.0

Also reproduced with older stable stack (not sure which version)

Method of installation

stack install of recent stack head, 4c38ee0

[gergoerdi]

FYI another ticket for this is #5486.

[snoyberg]

@haitlahcen hi-file-parser has been a source of a lot of issues like this, and is becoming a major blocker. I understand the goal you originally had in implementing it, but in its current state we'll likely need to remove the binary parsing code entirely unless you or someone else steps up to maintain the package.

[snoyberg]

Please see #5508