Re: Plan for GHC 8.6.1

Moritz Angermann
Hi,
I would almost go as far as saying 8.6 will work with LLVM4-6. GHC llvm codegen is really only dependent on the textual IR, and even there only on the parts we use. This used to be an issue, where LLVMs textual IR changed quite a bit, but it looks like it hasn't for the last few releases.
This of course does not insulate us from bugs in LLVM itself, which might or might not affect us.
Maybe we can be a bit more lenient with respect to LLVM versions?
I would really prefer not to be. We put in place the current policy for a few good reasons: not only was keeping up with the syntactic changes in a compatible way tiresome, but various sets of LLVM bugs meant significantly more work during ticket triage. While the relative syntactic stability of the last few LLVM releases may reduce the relevance of the first reason, the second reason holds just as well today as it did two years ago. Cheers, - Ben

I agree.
So back to my original question: will ghc 8.6.1 be moving to llvm 6 from
llvm 5?
Thanks
George
On Sun, Jun 24, 2018 at 12:11 PM Ben Gamari
Moritz Angermann
writes: Hi,
I would almost go as far as saying 8.6 will work with LLVM4-6. GHC llvm codegen is really only dependent on the textual IR, and even there only on the parts we use. This used to be an issue, where LLVMs textual IR changed quite a bit, but it looks like it hasn't for the last few releases.
This of course does not insulate us from bugs in LLVM itself, which might or might not affect us.
Maybe we can be a bit more lenient with respect to LLVM versions?
I would really prefer not to be. We put in place the current policy for a few good reasons: not only was keeping up with the syntactic changes in a compatible way tiresome, but various sets of LLVM bugs meant significantly more work during ticket triage.
While the relative syntactic stability of the last few LLVM releases may reduce the relevance of the first reason, the second reason holds just as well today as it did two years ago.
Cheers,
- Ben

current cabal has a nasty build failure on haddock errors, i'd really
appeciate some eyeballs / attention / ideas on how to get my fix / PR for
it over the finish line for GHC 8.6
https://github.com/haskell/cabal/pull/5269
(the issue is that haddock failures, such as on an empty package, fail an
entire build)
On Sun, Jun 24, 2018 at 12:56 PM Ben Gamari
George Colpitts
writes: I agree.
So back to my original question: will ghc 8.6.1 be moving to llvm 6 from llvm 5?
Ahh, whoops, missed the original question!
8.6 will use LLVM 6.0.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
participants (3)
-
Ben Gamari
-
Carter Schonwald
-
George Colpitts