Hi Erik,

That sounds great. Can your Jenkins instance maybe also push the reports to one 
of the GHC lists, so everybody can see what the state of play is?

Thanks,
Manuel

> Erik de Castro Lopo <[email protected]>:
> 
> Hi all,
> 
> As some of you may have noticed the LLVM requirements for GHC HEAD
> has just switched from version 3.6 to 3.7. This was mainly to support
> Arm64 (aka AArch64 aka Armv8-a), for which llvm-3.6 was badly broken.
> 
> Since figuring out what needed to change from 3.6 to 3.7 was rather
> painful, I decided to set up a small project to help us GHC devs
> keep up with what happens in the LLVM dev world.
> 
>  http://github.com/erikd/ghc-llvm-next/
> 
> The project is a build script (actually a Makefile) and a set of
> patches) which does the followiing:
> 
> * clones/updates LLVM from git, builds it and installs it locally
> * clones/updates GHC from git
> * applies patches git GHC so that GHC builds against the locally
> build LLVM tools.
> * builds GHC and then runs the testsuite
> 
> I plan on running the above build on a daily basis in my own 
> personal Jenkins instance in order to track changes in GHC and
> LLVM.
> 
> Others are free to do the same and I'm happy to take pull requests.
> This project may also be interesting or useful for people testing
> out up-coming LLVM features with GHC.
> 
> Cheers,
> Erik
> -- 
> ----------------------------------------------------------------------
> Erik de Castro Lopo
> http://www.mega-nerd.com/
> _______________________________________________
> ghc-devs mailing list
> [email protected]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________
ghc-devs mailing list
[email protected]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Reply via email to