[elemental-dev] Compiling with Clang 3.2

[Jack Poulson]

Dear all,

It seems that the current version of elemental-dev seems to have hit a bug in the backend of Clang 3.2. A bug report has been filed [http://llvm.org/bugs/show_bug.cgi?id=16361] and hopefully a workaround can be found soon.

Jack

[Jeff Hammond]

Then it could not be better timing that LLVM 3.3 was released yesterday :-)

Jeff

> --
> You received this message because you are subscribed to the Google Groups
> "elemental-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elemental-de...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Jeff Hammond
Argonne Leadership Computing Facility
University of Chicago Computation Institute
jham...@alcf.anl.gov / (630) 252-5381
http://www.linkedin.com/in/jeffhammond
https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond
ALCF docs: http://www.alcf.anl.gov/user-guides

[Jack Poulson]

Yes, but unfortunately 3.3 will not be the default version of Clang in standard Linux distributions for some time. I have not tested whether or not the bug is present in 3.3.

Jack

[Jeff Hammond]

Seems prudent to exploit preprocessor macros in CMake to prevent the
user from going down a doomed path...

> echo | clang -dM -E - | grep -i clang
#define __clang_major__ 3
#define __clang_minor__ 1
#define __clang_patchlevel__ 0

I'll update my local build of LLVM to the git master and see if this
is fixed yet and work back from there.

[Jack Poulson]

For what it's worth, I just verified that Elemental compiles with the trunk version of Clang.

Jack