Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
On 03/14/2013 02:15 PM, Jan Stolarek wrote: Hm, you're sure that LLVM 3.2 is in your path when you configure GHC? I removed LLVM 3.0 from my system so there's no possibility of mistaking 3.2 with 3.0. I'm also getting lots of compilation warnings about untested LLVM version - this didn't happen

Re: LLVM 3.2 failure

2013-03-14 Thread Austin Seipp
I was able to reproduce Geoffrey's failure on Mac OS X 10.8, with LLVM 3.2. The stage2 compiler eventually segfaults (Segmentation Fault 11) during the build process after being compiled successfully with stage1. Something recently happened, because I was bootstrapping fine with LLVM 3.2 recently

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
Where are all the fingerprints for the libraries? You only seem to have the submodule libraries in there... Geoff On 03/14/2013 03:00 PM, Jan Stolarek wrote: I'm attaching a fingerprint - is this OK? I'm quite puzzled about this, mostly because yesterday I couldn't build GHC using LLVM 3.0

Re: LLVM 3.2 failure

2013-03-14 Thread Jan Stolarek
Where are all the fingerprints for the libraries? You only seem to have the submodule libraries in there... Whoops, I ran the fingerprint script in the build tree which doesn't have symlinks to .git directories. Is this version of the fingerprint correct? Janek

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
I just tried building your fingerprinted tree here two different ways, and both failed: GHC 7.4.2 as bootstrap compiler + LLVM 3.2 GHC 7.6.2 as bootstrap compiler + LLVM 3.2 If you type llc -version at the command line, it really says it's 3.2? Geoff On 03/14/2013 03:06 PM, Jan Stolarek wrote:

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
On 03/14/2013 04:40 PM, Jan Stolarek wrote: If you type llc -version at the command line, it really says it's 3.2? You don't seem to believe me :) Given that Austin and I have the stage 2 compiler failure and you don't, I think it is reasonable do double check :) [killy@xerxes : ~] llc

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
At least they didn't re-roll the release tarball a second time :) Would be good to confirm that we built from the same source tree. I am building LLVM HEAD right now and will try that with GHC. Geoff On 03/14/2013 04:54 PM, Austin Seipp wrote: The LLVM 3.2 tarball has an annoying bug: it

Re: LLVM 3.2 failure

2013-03-14 Thread David Terei
urgh... really need to get a LLVM build bot up and running. I'm tied up for next week or two so won't be able to address this soon. Thanks though Austin for your work here and everyone else, great to have the pain shared :). Cheers, David On 14 March 2013 10:00, Geoffrey Mainland

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
My stage 2 compiler was crashing the first time it was invoked. I just finished building GHC HEAD using LLVM compiled from HEAD, and that worked, so perhaps this was just a 3.2 bug. I have yet to run the testsuite though. Geoff On 03/14/2013 07:16 PM, Jan Stolarek wrote: Goeff, Austin, do

Re: LLVM 3.2 failure

2013-03-14 Thread Austin Seipp
My stage2 compiler got built and also fails on any compilation, no matter how trivial. After linking stage2, my build fails with: $ make ===--- building phase 0 make -r --no-print-directory -f ghc.mk phase=0 phase_0_builds make[1]: Nothing to be done for `phase_0_builds'. ===--- building phase 1

Re: LLVM 3.2 failure

2013-03-14 Thread Geoffrey Mainland
On 03/14/2013 09:36 PM, Austin Seipp wrote: My stage2 compiler got built and also fails on any compilation, no matter how trivial. After linking stage2, my build fails with: $ make ===--- building phase 0 make -r --no-print-directory -f ghc.mk phase=0 phase_0_builds make[1]: Nothing to be