iliastsi wrote: > If this is the case, how have you been building GHC all this time? Were you > using LLVM 16?
@dyung Previous versions of GHC produced different code that didn't trigger this bug. This changed in GHC 9.10, with [this](https://gitlab.haskell.org/ghc/ghc/-/commit/c5d4916bc0970d0e3b3fb50cbcd7749065fd78fd) commit. > At this point in the release, we are only accepting patches for recent > regressions or major issues. Given this issues seems to have been around for > quite a while (and only seems to be hit in this one case), I am leaning > towards not merging this change into the 21.x release branch. I understand. In Debian, we have already backported this fix (see [here](https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/e6de8ff9d4a531b501184d1a672e3eaf2d1bf0ca), thank you @swt2c for this), so it's not urgent for us, but it would be nice if you consider backporting this, since LLVM 21 is currently the latest available LLVM version, and other distributions may also bump into this issue. https://github.com/llvm/llvm-project/pull/168380 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
