search for: pr6696

...ry). Now in 2.7 the JIT crashes when running out of memory. While that is a bug, I'm not sure if its part of the release criteria. I tried to make some changes in MallocSlabAllocator to not crash, but then FoldingSet crashed on OOM. P.S.: looking at the current 2.7 release blockers I only see PR6696 as relevant, the others are warnings, experimental code, and a fortran failure. Is that the case, or are the others release blockers too? Best regards, --Edwin

On 03/30/2010 09:15 PM, Tanya Lattner wrote: > > Thanks for testing the release! > >> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3, >> 64-bit. I built srcdir == objdir, I have built llvm and clang myself, >> and used the binaries for llvm-gcc. >> >> 1. llvm-gcc 2.7 vs 2.6 >> compared to my results from Aug 31 2009, ignoring CBE

There was a short discussion in the comments of PR6696 about Linux testing. The 2.7 release is slipping primarily because there are x86-32 problems to fix (there is also a Darwin problem and some other issues). We have two problems with our testing: The OSU/Google buildbots aren't running test-suite, apparently. I didn't realize that and as...

On Apr 6, 2010, at 9:52 AM, David Greene wrote: > There was a short discussion in the comments of PR6696 about Linux > testing. > > The 2.7 release is slipping primarily because there are x86-32 problems to > fix (there is also a Darwin problem and some other issues). > While lack of linux testing of the testsuite is a problem, this is not why the release is slipping. We need more pe...