search for: pr6270

Displaying 2 results from an estimated 2 matches for "pr6270".

Did you mean: p270
2011 Mar 18
0
[LLVMdev] [RC1] Status of Mingw MSYS
...yzer.cpp. (fixed in r127858) * RC1 3-stage build Please note configure and cmake will set optimizer option to -O2 by default even if clang++ were used. I overwrote for clang --with-optimize-option=-O3. Generated clang would be stable. But stage2-bin and stage3-bin will not match. Investigating. [PR6270] Without r127723, generated clang would be unavailable for parallel build. [PR9505] With -Asserts, I saw more two warnings, lib/Analysis/LazyValueInfo.cpp and lib/Transforms/Instrumentation/PathProfiling.cpp. * RC1 with patches. I have committed many patches for MSYS and mingw. With them, clang a...
2011 Mar 18
0
[LLVMdev] [RC1] Status of Visual Studio 8, 9 and 10
...point, r127264(in release_29/trunk) is needed to build with Debug on VS10. RC1 can pass clang-test with any configurations. RC1 fails llvm's check on many tests. * RC1 and patches ToT would be ready to failure-free build with several patches. - r127264 (in release_29/trunk) - r127723 [PR6270] PathV1::makeUnique() - r127731, r127732, r127733, r127734, r127775 [PR9234] test/CodeGen/X86 tweaks. - r127872 [PR6745] format("%e") Even with these patches, a few tests may fail. It seems {VS8 | VS10} Release are good. - VS8 Debug LLVM :: Transforms/SRETPromotion/basictest.l...