[Llvm-bgq-discuss] bgclang r205936-20140409 on vesta/mira

Biddiscombe, John A. biddisco at cscs.ch
Fri Apr 11 11:21:22 CDT 2014 

Hal

Ours is installed (correctly?) in

/bgsys/drivers/V1R2M1/ppc64/gnu-linux-4.7.2/

And the output of the link is here.

Thanks again

JB

bbpbg2:~/src/c++test$ bgclang++11 -O3 -o hello hello.cxx -dynamic -v
clang version 3.5.0 (trunk)
Target: powerpc64-bgq-linux
Thread model: posix
Found candidate GCC installation:
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6
Selected GCC installation:
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6
Candidate multilib: .;@m64
Selected multilib: .;@m64
 "/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/bin/c
lang" -cc1 -triple powerpc64-bgq-linux -S -disable-free -main-file-name
hello.cxx -mrelocation-model static -mdisable-fp-elim -ffp-contract=fast
-no-integrated-as -mconstructor-aliases -target-cpu a2q
-target-linker-version 2.20.51.0.2 -v -resource-dir
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/bin/../
lib/clang/3.5.0 -D __bgclang__=1 -D
"__bgclang_version__=\"r205936-20140409\"" -I
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/sleef/i
nclude -internal-isystem /usr/local/include -internal-isystem
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/bin/../
lib/clang/3.5.0/include -internal-externc-isystem /include
-internal-externc-isystem /usr/include -O3 -std=gnu++11 -fdeprecated-macro
-fno-dwarf-directory-asm -fdebug-compilation-dir
/gpfs/bbp.cscs.ch/home/biddisco/src/c++test -ferror-limit 19
-fmessage-length 129 -mstackrealign -fno-signed-char -fobjc-runtime=gcc
-fcxx-exceptions -fexceptions -fdiagnostics-show-option
-fcolor-diagnostics -vectorize-loops -vectorize-slp -isystem
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libc++/
include -isystem 
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libstdc
++fixup/include -isystem
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/include/c++/4.4.6
 -isystem 
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/include/c++/4.4.6
/powerpc64-bgq-linux -isystem
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/sys-include
-mllvm -optimize-regalloc -mllvm -fast-isel=0 -o /tmp/hello-57bca4.s -x
c++ hello.cxx
clang -cc1 version 3.5.0 based upon LLVM 3.5.0svn default target
powerpc64-unknown-linux-gnu
ignoring nonexistent directory
"/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libstd
c++fixup/include"
ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/sleef/
include
 /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libc++
/include
 /bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/include/c++/4.4.
6
 /bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/include/c++/4.4.
6/powerpc64-bgq-linux
 /bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/sys-include
 /usr/local/include
 /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/bin/..
/lib/clang/3.5.0/include
 /usr/include
End of search list.
 "/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/binut
ils/bin/as" -a64 -mppc64 -many -ma2q -o /tmp/hello-70bffe.o
/tmp/hello-57bca4.s
 "/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/binut
ils/bin/ld" --hash-style=gnu --no-add-needed --build-id --eh-frame-hdr -m
elf64ppc -dynamic-linker /lib64/ld64.so.1 -o hello
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/lib/crt1.o
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/lib/crti.o
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6/crt
begin.o 
-L/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libc+
+/lib -L/bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/lib
-L/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/sleef
/lib 
-L/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6
-L/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6/.
./../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64
-L/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6/.
./../../../powerpc64-bgq-linux/lib
-L/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6/.
./../.. 
-L/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/bin/.
./lib -L/lib -L/usr/lib -rpath
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libc++/
lib -rpath /bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/lib
/tmp/hello-70bffe.o -rpath
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/sleef/l
ib --as-needed -lsleef --no-as-needed -lc++ -lstdc++ -lm -lgcc_s -lgcc -lc
-lgcc_s -lgcc 
/bgsys/drivers/V1R2M1/ppc64/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.6/crt
end.o /bgsys/drivers/V1R2M1/ppc64/gnu-linux/powerpc64-bgq-linux/lib/crtn.o
/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-20140409/libc++/
lib/libc++.so: undefined reference to `vtable for
std::nested_exception at CXXABI_1.3.5'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)




On 11/04/14 17:53, "Hal Finkel" <hfinkel at anl.gov> wrote:

>John,
>
>I just noticed that, while I'm unable to reproduce this problem on our
>vesta system, I am able to reproduce the problem on our mira system. The
>reason is that on mira the 4.7.2 files ended up in a directory:
>
>/bgsys/drivers/toolchain/V1R2M1_base_4.7.2/V1R2M1_base_4.7.2/gnu-linux-4.7
>.2
>
>instead of:
>
>/bgsys/drivers/toolchain/V1R2M1_base_4.7.2/gnu-linux-4.7.2
>
>did something similar happen to you? Otherwise, can you please send the
>output of:
>
>bgclang++11 -O3 -o hello hello.cxx -dynamic -v
>
> -Hal
>
>----- Original Message -----
>> From: "John A. Biddiscombe" <biddisco at cscs.ch>
>> To: "Hal Finkel" <hfinkel at anl.gov>
>> Cc: llvm-bgq-discuss at lists.alcf.anl.gov, "Thomas Heller"
>><thom.heller at gmail.com>
>> Sent: Friday, April 11, 2014 7:45:49 AM
>> Subject: RE: [Llvm-bgq-discuss] bgclang r205936-20140409 on vesta/mira
>> 
>> bbpbgas033:~/src/c++test$ cat hello.cxx
>> #include <stdio.h>
>> #include <string.h>
>> #include <errno.h>
>> 
>> #include <sys/types.h>
>> #include <sys/stat.h>
>> #include <fcntl.h>
>> 
>> #include <iostream>
>> 
>> int main(int argc, char **argv)
>> {
>>   std::cout << "Hello " << std::endl;
>> }
>> 
>> apologies for the surplus #includes
>> 
>> 
>> > -----Original Message-----
>> > From: Hal Finkel [mailto:hfinkel at anl.gov]
>> > Sent: 11 April 2014 14:45
>> > To: Biddiscombe, John A.
>> > Cc: llvm-bgq-discuss at lists.alcf.anl.gov; Thomas Heller
>> > Subject: Re: [Llvm-bgq-discuss] bgclang r205936-20140409 on
>> > vesta/mira
>> > 
>> > What's in your hello.cxx?
>> > 
>> >  -Hal
>> > 
>> > ----- Original Message -----
>> > > From: "John A. Biddiscombe" <biddisco at cscs.ch>
>> > > To: "Hal Finkel" <hfinkel at anl.gov>, "Thomas Heller"
>> > > <thom.heller at gmail.com>
>> > > Cc: llvm-bgq-discuss at lists.alcf.anl.gov
>> > > Sent: Friday, April 11, 2014 7:42:25 AM
>> > > Subject: RE: [Llvm-bgq-discuss] bgclang r205936-20140409 on
>> > > vesta/mira
>> > >
>> > > Hal,
>> > >
>> > > I have
>> > >
>> > > CC="/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/bin/bgclang"
>> > >
>> > CXX="/gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/bin/bgclang++1
>> > 1"
>> > >
>> > > after a bit of experimentation, I found that $CC hello.c -o hello
>> > > works fine and executable runs on login and ION
>> > >
>> > > $CXX hello.cxx -o hello
>> > > gives the link error
>> > >
>> > > but
>> > >
>> > /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/mpi/bgclang/bin/mpi
>> > > c++
>> > > hello.cxx -o hello
>> > > works for a non mpi application on login and ION
>> > >
>> > > and for an mpi aplication
>> > >
>> > /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/mpi/bgclang/bin/mpi
>> > > c++
>> > > hellompi.cxx -o hello
>> > > compiles ok, but on execution dies on login and ION
>> > >
>> > > bbpbg2:~/src/c++test$ mpiexec -n 1 ./hello
>> > >
>> > /bgsys/source/srcV1R2M1.17463/comm/sys/buildtools/pami/common/bgq/
>> > BgqPersonality.h:102:
>> > >
>> > /bgsys/source/srcV1R2M1.17463/comm/sys/buildtools/pami/common/bgq/
>> > BgqP
>> > > ersonality.h<102>
>> > >
>> > >
>> > ==========================================================
>> > ===========================
>> > > =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>> > > =   EXIT CODE: 134
>> > > =   CLEANING UP REMAINING PROCESSES
>> > > =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>> > >
>> > ==========================================================
>> > ============
>> > > =============== APPLICATION TERMINATED WITH THE EXIT STRING:
>> > Aborted
>> > > (signal 6)
>> > >
>> > >
>> > > Not sure if this helps you, but it's interesting that mpic++
>> > > links ok,
>> > > when c++ does not, I use c++ compiler by default and link mkpi
>> > > stuff
>> > > myself (I don't use the mpi wrappers generally)
>> > >
>> > > JB
>> > >
>> > > > -----Original Message-----
>> > > > From: Hal Finkel [mailto:hfinkel at anl.gov]
>> > > > Sent: 11 April 2014 14:19
>> > > > To: Thomas Heller
>> > > > Cc: Biddiscombe, John A.; llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > Subject: Re: [Llvm-bgq-discuss] bgclang r205936-20140409 on
>> > > > vesta/mira
>> > > >
>> > > > I'll look into this today.
>> > > >
>> > > >  -Hal
>> > > >
>> > > > ----- Original Message -----
>> > > > > From: "Thomas Heller" <thom.heller at gmail.com>
>> > > > > To: "John A. Biddiscombe" <biddisco at cscs.ch>,
>> > > > > llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > Sent: Friday, April 11, 2014 6:19:32 AM
>> > > > > Subject: Re: [Llvm-bgq-discuss] bgclang r205936-20140409 on
>> > > > > vesta/mira
>> > > > >
>> > > > > On 04/11/2014 12:48 PM, Biddiscombe, John A. wrote:
>> > > > > > oops, I think I pasted the wrong error into my email, the
>> > > > > > actual
>> > > > > > one I can't make go away is this
>> > > > > >
>> > > > > > /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/bgclang/r205936-
>> > > > 20140409/libc++/lib/libc++.so:
>> > > > > > undefined reference to `vtable for
>> > > > > > std::nested_exception at CXXABI_1.3.5' clang: error: linker
>> > > > > > command
>> > > > > > failed with exit code 1 (use -v to see invocation)
>> > > > > >
>> > > > > > any suggestions welcome.
>> > > > >
>> > > > > I haven't seen this error before ...
>> > > > >
>> > > > > >
>> > > > > > JB
>> > > > > >
>> > > > > >
>> > > > > >> -----Original Message-----
>> > > > > >> From: llvm-bgq-discuss-bounces at lists.alcf.anl.gov
>> > > > > >> [mailto:llvm-bgq-discuss-
>> > > > > >> bounces at lists.alcf.anl.gov] On Behalf Of Thomas Heller
>> > > > > >> Sent: 11 April 2014 12:42
>> > > > > >> To: llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >> Subject: Re: [Llvm-bgq-discuss] bgclang r205936-20140409
>> > > > > >> on
>> > > > > >> vesta/mira
>> > > > > >>
>> > > > > >> John,
>> > > > > >>
>> > > > > >> I have a dirty workaround for this in HPX ... let me
>> > > > > >> commit
>> > > > > >> real quick (not sure where this comes from though)
>> > > > > >>
>> > > > > >> On 04/11/2014 12:03 PM, Biddiscombe, John A. wrote:
>> > > > > >>> Hal
>> > > > > >>>
>> > > > > >>> We have the toolchain_4.7.2  files installed in what I
>> > > > > >>> believe
>> > > > > >>> is the default location, recompiling boost+hpx still
>> > > > > >>> gives me
>> > > > > >>> the std::exception link errors, if I add
>> > > > > >>>
>> > > > > >>> /bgsys/drivers/V1R2M1/ppc64/gnu-linux-4.7.2/powerpc64-bgq-
>> > linu
>> > > > > >>> x/li
>> > > > > >>> b/li
>> > > > > >>> bstdc++.a
>> > > > > >>>
>> > > > > >>> to the link libs, then all the errors go away except this
>> > > > > >>> one
>> > > > > >>>
>> > > > > >>> ../../../../lib/hpx/libhpxd.so.0.9.9: undefined reference
>> > > > > >>> to
>> > > > > >> `boost::re_detail::perl_matcher<std::__1::__wrap_iter<char
>> > > > > >> const*>,
>> > > > > >> 
>>std::__1::allocator<boost::sub_match<std::__1::__wrap_iter<char
>> > > > > >> const*> >
>> > > > > >>> , boost::regex_traits<char, boost::cpp_regex_traits<char>
>> > > > > >>> >
>> > > > > >>> >::match()'
>> > > > > >>>
>> > > > > >>> Which looks like a -stdlib=c++ problem.
>> > > > > >>>
>> > > > > >>> Can you tell me what setting you use to compile boost
>> > > > > >>> with?
>> > > > > >>> I've
>> > > > > >>> been using # user-config.jam (put this file into your
>> > > > > >>> home
>> > > > > >>> directory) using clang
>> > > > > >>>     :
>> > > > > >>>     : bgclang++11
>> > > > > >>>     : <cxxflags> -std=c++0x
>> > > > > >>>     ;
>> > > > > >>>
>> > > > > >>> and tried adding/removing -stdlib=libc++ or
>> > > > > >>> -stdlib=stdc++,
>> > > > > >>> but so far no
>> > > > > >> success.
>> > > > > >>>
>> > > > > >>> yours
>> > > > > >>>
>> > > > > >>> JB
>> > > > > >>>
>> > > > > >>>
>> > > > > >>>> -----Original Message-----
>> > > > > >>>> From: Hal Finkel [mailto:hfinkel at anl.gov]
>> > > > > >>>> Sent: 10 April 2014 19:41
>> > > > > >>>> To: Biddiscombe, John A.
>> > > > > >>>> Cc: llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>> Subject: Re: [Llvm-bgq-discuss] bgclang r205936-20140409
>> > > > > >>>> on
>> > > > > >>>> vesta/mira
>> > > > > >>>>
>> > > > > >>>> John,
>> > > > > >>>>
>> > > > > >>>> Yes, this looks exactly like the issue that really
>> > > > > >>>> motivated
>> > > > > >>>> the switch. There are necessary symbols that are just
>> > > > > >>>> missing
>> > > > > >>>> from the old 4.4.6 libraries (the situation is somewhat
>> > > > > >>>> complicated because the compiler actually generated
>> > > > > >>>> multiple
>> > > > > >>>> version of these destructors, and the older gcc did not
>> > > > > >>>> generate all of them). As I said,
>> > > > > >> please let me know if you can't get the files.
>> > > > > >>>>
>> > > > > >>>>    -Hal
>> > > > > >>>>
>> > > > > >>>> ----- Original Message -----
>> > > > > >>>>> From: "John A. Biddiscombe" <biddisco at cscs.ch>
>> > > > > >>>>> To: "Hal Finkel" <hfinkel at anl.gov>
>> > > > > >>>>> Cc: llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>> Sent: Thursday, April 10, 2014 12:30:12 PM
>> > > > > >>>>> Subject: Re: [Llvm-bgq-discuss] bgclang
>> > > > > >>>>> r205936-20140409 on
>> > > > > >>>>> vesta/mira
>> > > > > >>>>>
>> > > > > >>>>> Hal
>> > > > > >>>>>
>> > > > > >>>>> Linking CXX executable ../../../../bin/network_storage
>> > > > > >>>>> CMakeFiles/network_storage_exe.dir/network_storage.cpp.o:
>> > > > > >>>>> In
>> > > > > >>>>> function
>> > > > > >>>>> `current_exception_std_exception_wrapper':
>> > > > > >>>>>
>> > > > > >>>>
>> > > > > >>
>> > > >
>> > /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/boost_1_55_0/include/boo
>> > > > > >> st
>> > > > > >>>> -
>> > > > > >>>>> 1_55/
>> > > > > >>>>> boost/exception/detail/exception_ptr.hpp:220: undefined
>> > > > > >>>>> reference to `std::domain_error::~domain_error()'
>> > > > > >>>>> CMakeFiles/network_storage_exe.dir/network_storage.cpp.o:
>> > > > > >>>>> In
>> > > > > >>>>> function
>> > > > > >>>>> `~current_exception_std_exception_wrapper':
>> > > > > >>>>>
>> > > > > >>>>
>> > > > > >>
>> > > >
>> > /gpfs/bbp.cscs.ch/home/biddisco/apps/clang/boost_1_55_0/include/boo
>> > > > > >> st
>> > > > > >>>> -
>> > > > > >>>>> 1_55/
>> > > > > >>>>> boost/exception/detail/exception_ptr.hpp:224: undefined
>> > > > > >>>>> reference to `std::domain_error::~domain_error()'
>> > > > > >>>>> …. + million more
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>> I have to go out now, so I can’t play, but if those
>> > > > > >>>>> errors
>> > > > > >>>>> look like a
>> > > > > >>>>> libstdc++ issue then I might need those 4.7.2 files…
>> > > > > >>>>>
>> > > > > >>>>> Cheers
>> > > > > >>>>>
>> > > > > >>>>> JB
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>> On 10/04/14 19:06, "Hal Finkel" <hfinkel at anl.gov>
>> > > > > >>>>> wrote:
>> > > > > >>>>>
>> > > > > >>>>>> I'll also add that all V1R2M1 installs (as far as I
>> > > > > >>>>>> know)
>> > > > > >>>>>> use
>> > > > > >>>>>> 4.4.6
>> > > > > >>>>>> by default. The 4.7.2 files are supplementary; you (or
>> > > > > >>>>>> your
>> > > > > >>>>>> system
>> > > > > >>>>>> admins)
>> > > > > >>>>>> just need to unpack them.
>> > > > > >>>>>>
>> > > > > >>>>>> -Hal
>> > > > > >>>>>>
>> > > > > >>>>>> ----- Original Message -----
>> > > > > >>>>>>> From: "Hal Finkel" <hfinkel at anl.gov>
>> > > > > >>>>>>> To: "John A. Biddiscombe" <biddisco at cscs.ch>
>> > > > > >>>>>>> Cc: llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>> Sent: Thursday, April 10, 2014 12:04:16 PM
>> > > > > >>>>>>> Subject: Re: [Llvm-bgq-discuss] bgclang
>> > > > > >>>>>>> r205936-20140409
>> > > > > >>>>>>> on vesta/mira
>> > > > > >>>>>>>
>> > > > > >>>>>>> No problem; to be clear, the files from the 4.7.2
>> > > > > >>>>>>> toolchain that are used by bgclang should not really
>> > > > > >>>>>>> be
>> > > > > >>>>>>> sensitive to the driver version you're actually
>> > > > > >>>>>>> using. If,
>> > > > > >>>>>>> however, you have any problems with the new build,
>> > > > > >>>>>>> please
>> > > > > >>>>>>> let me know.
>> > > > > >>>>>>>
>> > > > > >>>>>>>    -Hal
>> > > > > >>>>>>>
>> > > > > >>>>>>> ----- Original Message -----
>> > > > > >>>>>>>> From: "John A. Biddiscombe" <biddisco at cscs.ch>
>> > > > > >>>>>>>> To: "John A. Biddiscombe" <biddisco at cscs.ch>, "Hal
>> > > > > >>>>>>>> Finkel"
>> > > > > >>>>>>>> <hfinkel at anl.gov>,
>> > > > > >>>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>>> Sent: Thursday, April 10, 2014 12:00:34 PM
>> > > > > >>>>>>>> Subject: Re: [Llvm-bgq-discuss] bgclang
>> > > > > >>>>>>>> r205936-20140409
>> > > > > >>>>>>>> on vesta/mira
>> > > > > >>>>>>>>
>> > > > > >>>>>>>> Sorry, rereading what you wrote the answer must be
>> > > > > >>>>>>>> no. I
>> > > > > >>>>>>>> was confused because we have V1R2M1, but use 4.4.6
>> > > > > >>>>>>>>
>> > > > > >>>>>>>> JB
>> > > > > >>>>>>>>
>> > > > > >>>>>>>> On 10/04/14 18:55, "Biddiscombe, John A."
>> > > > > >>>>>>>> <biddisco at cscs.ch>
>> > > > > >>>>>>>> wrote:
>> > > > > >>>>>>>>
>> > > > > >>>>>>>>> Hal,
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> 1. The toolchain is now setup to use
>> > > > > >>>>>>>>>> libc/libstdc++
>> > > > > >>>>>>>>>> files
>> > > > > >>>>>>>>> >from  the
>> > > > > >>>>>>>>>> /bgsys/drivers/toolchain/V1R2M1_base_4.7.2 -- this
>> > > > > >>>>>>>>>> gives access to a more-recent environment for
>> > > > > >>>>>>>>>> C/C++03
>> > > > > >>>>>>>>>> compilation, and furthermore, is necessary to make
>> > > > > >>>>>>>>>> (at
>> > > > > >>>>>>>>>> least one part of) Boost work with
>> > > > > >>>>>>>>>> bgclang++11. You
>> > > > > >>>>>>>>>> don't need to be on a system running V1R2M1 (Mira
>> > > > > >>>>>>>>>> is
>> > > > > >>>>>>>>>> not yet, for
>> > > > > >>>>>>>>>> example) to make use of this.
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>> We don’t have the toolchain 4.7.2 on our system.
>> > > > > >>>>>>>>> Does
>> > > > > >>>>>>>>> that mean I can’t use the new compiler? We have
>> > > > > >>>>>>>>> only
>> > > > > >>>>>>>>> files from
>> > > > > >>>>>>>>> 4.4.6 :(
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>> Thanks
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>> JB
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> 2. There are more OpenMP 4 features available for
>> > > > > >>>>>>>>>> you
>> > > > > >>>>>>>>>> to play
>> > > > > >>>>>>>>>> with:
>> > > > > >>>>>>>>>>     - '#pragma omp simd' (and friends) should now
>> > > > > >>>>>>>>>>     work
>> > > > > >>>>>>>>>>     (in
>> > > > > >>>>>>>>>>     the
>> > > > > >>>>>>>>>>     sense
>> > > > > >>>>>>>>>>     that
>> > > > > >>>>>>>>>> there is a reasonable probability that it will
>> > > > > >>>>>>>>>> cause
>> > > > > >>>>>>>>>> QPX to be
>> > > > > >>>>>>>>>> generated)
>> > > > > >>>>>>>>>>     - '#pragma omp task depend(...)' is supported
>> > > > > >>>>>>>>>>     (for
>> > > > > >>>>>>>>>>     the
>> > > > > >>>>>>>>>>     most
>> > > > > >>>>>>>>>>     part; I
>> > > > > >>>>>>>>>> think there are still some corner cases where the
>> > > > > >>>>>>>>>> compiler support is ahead of the runtime).
>> > > > > >>>>>>>>>>      Please try these things out and let me know
>> > > > > >>>>>>>>>>      what
>> > > > > >>>>>>>>>>      you
>> > > > > >>>>>>>>>>      find.
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> For those maintaining their own installs, RPMs
>> > > > > >>>>>>>>>> (and
>> > > > > >>>>>>>>>> SRPMs)
>> > > > > >>>>>>>>>> are available on the trac page:
>> > > > > >>>>>>>>>> https://trac.alcf.anl.gov/projects/llvm-bgq
>> > > > > >>>>>>>>>> --
>> > > > > >>>>>>>>>> If
>> > > > > >>>>>>>>>> your
>> > > > > >>>>>>>>>> system does not have
>> > > > > >>>>>>>>>> /bgsys/drivers/toolchain/V1R2M1_base_4.7.2
>> > > > > >>>>>>>>>> unpacked,
>> > > > > >>>>>>>>>> and you can't get a copy of those files, please
>> > > > > >>>>>>>>>> let me
>> > > > > >>>>>>>>>> know.
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> Finally, for those strange creatures wanting to
>> > > > > >>>>>>>>>> run the
>> > > > > >>>>>>>>>> compiler
>> > > > > >>>>>>>>> >from the
>> > > > > >>>>>>>>>> A2 login or I/O nodes, I believe this build should
>> > > > > >>>>>>>>>> now
>> > > > > >>>>>>>>>> work for you again. ;)
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> Thanks again,
>> > > > > >>>>>>>>>> Hal
>> > > > > >>>>>>>>>>
>> > > > > >>>>>>>>>> --
>> > > > > >>>>>>>>>> Hal Finkel
>> > > > > >>>>>>>>>> Assistant Computational Scientist Leadership
>> > > > > >>>>>>>>>> Computing
>> > > > > >>>>>>>>>> Facility Argonne National Laboratory
>> > > > > >>>>>>>>>>
>> > _______________________________________________
>> > > > > >>>>>>>>>> llvm-bgq-discuss mailing list
>> > > > > >>>>>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>>>>>
>>https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-di
>> > > > > >>>>>>>>>> scus
>> > > > > >>>>>>>>>> s
>> > > > _______________________________________________
>> > > > > >>>>>>>>>> llvm-bgq-discuss mailing list
>> > > > > >>>>>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>>>>>
>>https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-di
>> > > > > >>>>>>>>>> scus
>> > > > > >>>>>>>>>> s
>> > > > _______________________________________________
>> > > > > >>>>>>>>>> llvm-bgq-discuss mailing list
>> > > > > >>>>>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>>>>>
>>https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-di
>> > > > > >>>>>>>>>> scus
>> > > > > >>>>>>>>>> s
>> > > > > >>>>>>>>>
>> > > > > >>>>>>>>>
>> > _______________________________________________
>> > > > > >>>>>>>>> llvm-bgq-discuss mailing list
>> > > > > >>>>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>>>>
>>https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-dis
>> > > > > >>>>>>>>> cuss
>> > > > > >>>>>>>>
>> > > > > >>>>>>>>
>> > > > > >>>>>>>
>> > > > > >>>>>>> --
>> > > > > >>>>>>> Hal Finkel
>> > > > > >>>>>>> Assistant Computational Scientist Leadership
>> > > > > >>>>>>> Computing
>> > > > > >>>>>>> Facility Argonne National Laboratory
>> > > > > >>>>>>> _______________________________________________
>> > > > > >>>>>>> llvm-bgq-discuss mailing list
>> > > > > >>>>>>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>>>>>> 
>>https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discu
>> > > > > >>>>>>> ss
>> > > > > >>>>>>>
>> > > > > >>>>>>
>> > > > > >>>>>> --
>> > > > > >>>>>> Hal Finkel
>> > > > > >>>>>> Assistant Computational Scientist Leadership Computing
>> > > > > >>>>>> Facility Argonne National Laboratory
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>
>> > > > > >>>> --
>> > > > > >>>> Hal Finkel
>> > > > > >>>> Assistant Computational Scientist
>> > > > > >>>> Leadership Computing Facility
>> > > > > >>>> Argonne National Laboratory
>> > > > > >>> _______________________________________________
>> > > > > >>> llvm-bgq-discuss mailing list
>> > > > > >>> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >>> https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discuss
>> > > > > >>>
>> > > > > >>
>> > > > > >>
>> > > > > >> --
>> > > > > >> Thomas Heller
>> > > > > >> Friedrich-Alexander-Universität Erlangen-Nürnberg
>> > > > > >> Department
>> > > > > >> Informatik -
>> > > > > >> Lehrstuhl Rechnerarchitektur Martensstr. 3
>> > > > > >> 91058 Erlangen
>> > > > > >> Tel.: 09131/85-27018
>> > > > > >> Fax:  09131/85-27912
>> > > > > >> Email: thomas.heller at cs.fau.de
>> > > > > >> _______________________________________________
>> > > > > >> llvm-bgq-discuss mailing list
>> > > > > >> llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > >> https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discuss
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Thomas Heller
>> > > > > Friedrich-Alexander-Universität Erlangen-Nürnberg
>> > > > > Department Informatik - Lehrstuhl Rechnerarchitektur
>> > > > > Martensstr. 3
>> > > > > 91058 Erlangen
>> > > > > Tel.: 09131/85-27018
>> > > > > Fax:  09131/85-27912
>> > > > > Email: thomas.heller at cs.fau.de
>> > > > > _______________________________________________
>> > > > > llvm-bgq-discuss mailing list
>> > > > > llvm-bgq-discuss at lists.alcf.anl.gov
>> > > > > https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discuss
>> > > > >
>> > > >
>> > > > --
>> > > > Hal Finkel
>> > > > Assistant Computational Scientist
>> > > > Leadership Computing Facility
>> > > > Argonne National Laboratory
>> > >
>> > 
>> > --
>> > Hal Finkel
>> > Assistant Computational Scientist
>> > Leadership Computing Facility
>> > Argonne National Laboratory
>> 
>
>-- 
>Hal Finkel
>Assistant Computational Scientist
>Leadership Computing Facility
>Argonne National Laboratory

More information about the llvm-bgq-discuss mailing list