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
GHC uses nm to find the sizes of some things when building, but llvm-nm doesn't quite work for WebAssembly (or -flto for that matter). They tried fixing it once, but llvm-nm now shows the offset information, not the size information as expected.
We currently have a hacky fix that uses -flto to trick GHC into producing LLVM bitcode, which we then llvm-dis to get the necessary information out of. I find it rather amusing that this works, but it's obviously a terrible solution.
GHC uses
nm
to find the sizes of some things when building, butllvm-nm
doesn't quite work for WebAssembly (or-flto
for that matter). They tried fixing it once, but llvm-nm now shows the offset information, not the size information as expected.We currently have a hacky fix that uses
-flto
to trick GHC into producing LLVM bitcode, which we thenllvm-dis
to get the necessary information out of. I find it rather amusing that this works, but it's obviously a terrible solution.We have a ticket in with LLVM:
https://bugs.llvm.org/show_bug.cgi?id=34392
The text was updated successfully, but these errors were encountered: