-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/08/12 05:30, Jeff Squyres wrote:
> I see a clang 3.1 on http://llvm.org/releases/, but I
> don't see a 4.0. Is that a released version?
Thanks to a colleague at VLSCI who's got Mountain Lion the version
information for clang and llvm-gcc are a
On Mon, Aug 20, 2012 at 12:30 PM, Jeff Squyres wrote:
> I see a clang 3.1 on http://llvm.org/releases/, but I don't see a 4.0. Is
> that a released version?
Apple Clang has a different and unrelated version numbering compared
to open source clang.
Dmitri
--
main(i,j){for(i=2;;i++){for(j=2;j*
Mountain Lion ships with 4.0
Guess I could give it a shot, but I never use clang myself.
On Aug 20, 2012, at 12:30 PM, Jeff Squyres wrote:
> Hmm. That sucks.
>
> I have Lion, not Mountain Lion. All those tests pass for me with both:
>
> [15:28] jsquyres-mac:~ % clang --version
> Apple cla
Hmm. That sucks.
I have Lion, not Mountain Lion. All those tests pass for me with both:
[15:28] jsquyres-mac:~ % clang --version
Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix
and
[15:28] jsquyres-mac:~ % gcc --
Thanks for the new 1.6.1rc3. It compiles well, but
I get 3 of 5 tests failed on OSX 10.8 using clang-4.0.
The output is here:
https://gist.github.com/3388612
If there is specific output from the failing tests you need,
let me know how to generate it. When I compile and test
with llvm-gcc-4.2.1,
