search for: libiomp5

...t 11:18:35PM +0300, Andrey Bokhanko wrote: > 3) Some people believe that libiomp is not a proper name anymore and > should be changed. I'm not a library expert, so really don't know. > However, this means that we should flip default library setting ASAP. > Why? Because now "libiomp5" is a user-visible name (one has to use > "-fopenmp=libiomp5" to enable OpenMP in clang) and the sooner it will > become non user-visible, the better. Any objections here? Switch the library name together with the default value for clang. That seems like to the way forward. It...

Jack, this is not a problem of this patch, this a problem of your configuration. This patch uses standard clang machinery for locating libiomp5 library. Best regards, Alexey Bataev ============= Software Engineer Intel Compiler Team 13.05.2015 15:59, Jack Howarth пишет: > On Tue, May 12, 2015 at 3:58 PM, <andreybokhanko at gmail.com> wrote: >> Jack, >> >> Alexey [Bataev] promised to send it for review in a day...

...or switching the -fopenmp support over >>>>> to the openmp library instead of libgomp? I realize the call to rename >>>>> the library may be complicating this process. Perhaps the switch of >>>>> the default library should be done first under the current libiomp5 >>>>> name and that tested for a few days first before using follow on >>>>> patches to switch the library name to llomp or whatever. I would be >>>>> nice to no longer have to feed clang "-fopenmp=libiomp5 -Xclang >>>>> -fopenmp=libi...

...л(а): > > Is there a proposed patch yet for switching the -fopenmp support over > to the openmp library instead of libgomp? I realize the call to rename > the library may be complicating this process. Perhaps the switch of > the default library should be done first under the current libiomp5 > name and that tested for a few days first before using follow on > patches to switch the library name to llomp or whatever. I would be > nice to no longer have to feed clang "-fopenmp=libiomp5 -Xclang > -fopenmp=libiomp5". > Jack > > On Fri, May 8, 2015 a...

...e a proposed patch yet for switching the -fopenmp support over >>> to the openmp library instead of libgomp? I realize the call to rename >>> the library may be complicating this process. Perhaps the switch of >>> the default library should be done first under the current libiomp5 >>> name and that tested for a few days first before using follow on >>> patches to switch the library name to llomp or whatever. I would be >>> nice to no longer have to feed clang "-fopenmp=libiomp5 -Xclang >>> -fopenmp=libiomp5". >>>...

...i++) > ^ > magick/attribute.c:972:9: note: loop iteration variable is predetermined as > linear > i; > ^ > 2 errors generated. > > I get the same error when I try to build the latest ImageMagick 6.9.1-2 > sources with clang 3.7svn using -fopenmp=libiomp5 -Xclang -fopenmp=libiomp5. > >> >> Is there a generous soul (not employed by a CPU vendor :-)) willing to run >> "John the Ripper" with "clang -fopenmp=libiomp5 -Xclang -fopenmp=libiomp5 >> -lm -O3" and compare results with "clang -O3"? >&...

On Thu, May 7, 2015 at 10:53 PM, Hans Wennborg <hans at chromium.org> wrote: > Congratulations! Would you like to add a blurb to the release notes > for the next release? Sure! Will do. Yours, Andrey

Hal, On Thu, Apr 30, 2015 at 5:06 PM, Hal Finkel <hfinkel at anl.gov> wrote: > We need to get the build system integration committed and the buildbots > updated to compile it > If you are speaking on libiomp buidbots, they are already established: http://lab.llvm.org:8011/builders/libiomp5-clang-x86_64-linux-debian http://lab.llvm.org:8011/builders/libiomp5-gcc-x86_64-linux-debian Andrey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150501/c17880e5/attachment.html>

...rom inside the build folder: ------------------------- $ldd bin/exec/R linux-vdso.so.1 (0x00007ffc1e853000) libR.so => /usr/lib64/R/lib/libR.so (0x00007f747091f000) libRblas.so => not found !! is not yet installed in the machine !! libm.so.6 => /lib64/libm.so.6 (0x00007f7470616000) libiomp5.so => /opt/intel/lib/intel64_lin/libiomp5.so (0x00007f74702d5000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f74700be000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f746fea1000) libc.so.6 => /lib64/libc.so.6 (0x00007f746fae1000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f746f...

...ix.com/scan.php?page=article&item=clang-gcc-broadwell&num=3) and ImageMagick -- though latter is not included in most recent "clang vs gcc" comparison. Is there a generous soul (not employed by a CPU vendor :-)) willing to run "John the Ripper" with "clang -fopenmp=libiomp5 -Xclang -fopenmp=libiomp5 -lm -O3" and compare results with "clang -O3"? Also, Jack Howarth did testing with some other benchmarks, and it is nice to see that clang + libiomp compare quite well (to say it mildly ;-)) with gcc + libgomp! Andrey -------------- next part -------------...

...llvm/clang/compiler-rt/openmp svn on Mac OS X 10.9 out of tree with… pushd projects/openmp/runtime make compiler=clang popd and then OPENMP_DIR=`ls projects/openmp/runtime/tmp | grep dyn` pushd projects/openmp/runtime/tmp/$OPENMP_DIR install -m 755 libiomp5.dylib %i/opt/llvm-%v/lib/libgomp.dylib install -m 644 *.h %i/opt/llvm-%v/lib/clang/%v/include popd in our fink llvm packaging. It would be nice to see the cmake build machinery updated to automatically build and install openmp if its sources are placed in the projects subdirect...

...pushd projects/openmp/runtime >> make compiler=clang >> popd >> >> and then >> >> OPENMP_DIR=`ls projects/openmp/runtime/tmp | grep dyn` >> pushd projects/openmp/runtime/tmp/$OPENMP_DIR >> install -m 755 libiomp5.dylib %i/opt/llvm-%v/lib/libgomp.dylib >> install -m 644 *.h %i/opt/llvm-%v/lib/clang/%v/include >> popd >> >> in our fink llvm packaging. >> It would be nice to see the cmake build machinery updated to >> automatically build and install openm...

...------------------------------------------- > > $ ldd bin/exec/R > > linux-vdso.so.1 (0x00007ffe073f3000) > > libR.so => /usr/lib64/R/lib/libR.so (0x00007f43939e6000) > > libRblas.so => not found > > libm.so.6 => /lib64/libm.so.6 (0x00007f43936de000) > > libiomp5.so => /opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64/libiomp5.so > > (0x00007f439339c000) > > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4393185000) > > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4392f69000) > > libc.so.6 =>...

...ue so serious that it will be blocker for the current >> patches to enabled the openmp build from within llvm/projects? Can't we >> just proceed with the current library name until the top-level openmp build >> infrastructure added and the switch of the default for -fopenmp to libiomp5 >> is made. It seems more sensible to stabilize the openmp support first and >> then revisit the naming issue in a couple of weeks. >> > > For me, I would prefer that the default switch for -fopenmp be towards the > new name. > > I freely admit this is a non-technic...

...th no $ make install, I get this: -------------------------------------------------------------------- $ ldd bin/exec/R linux-vdso.so.1 (0x00007ffe073f3000) libR.so => /usr/lib64/R/lib/libR.so (0x00007f43939e6000) libRblas.so => not found libm.so.6 => /lib64/libm.so.6 (0x00007f43936de000) libiomp5.so => /opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64/libiomp5.so (0x00007f439339c000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4393185000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4392f69000) libc.so.6 => /lib64/libc.so.6 (0x00007f4392ba8000) li...

On Wed, Sep 9, 2015 at 11:26 PM, Nathan Kurz <nate at verse.com> wrote: > > As a short and simple approach, I just compiled the current R release > on Ubuntu with ICC and MKL using just this: > > $ tar -xzf R-3.2.2.tar.gz > $ cd R-3.2.2 > $ CC=icc CXX=icpc AR=xiar LD=xild CFLAGS="-g -O3 -xHost" CXXFLAGS="-g > -O3 -xHost" ./configure

...ThinLTO not finishing, I'll consider copying those to the local build tree first. > Can you nm the .so files in your lib dir and see if any reference > __morestack? $ for so in lib/*.so; do echo $so ; nm $so|grep __morestack;done lib/BugpointPasses.so lib/libclang.so lib/libgomp.so lib/libiomp5.so lib/liblldb.so U __morestack lib/libLTO.so lib/libomp.so lib/LLVMgold.so lib/LLVMHello.so lib/LLVMPolly.so Looks like liblldb.so does. Does that explain anything?

Hi, I want to convert LLVM bitcode files to cpp. I use these commands: 1. clang -c -emit-llvm -fopenmp=libiomp5 oh2.c -o oh2.bc2. llc -march=cpp oh2.bc -o oh2.cpp3. g++ -fno-rtti -O0 -g `$HOME/llvmbuild/bin/llvm-config --cxxflags` oh2.cpp `$HOME/llvmbuild/bin/llvm-config --ldflags --libs --system-libs` -o oh2c After the 3rd command, I get a lot of compilation errors. Is it possible that llc -march=cpp genera...

All, I'd like to resurrect the discussion on replacing libgomp with libiomp as the default OpenMP runtime library linked with -fopenmp. For reference, the previous discussion is accessible there: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140217/thread.html#99461 We are very close to getting *full* OpenMP 3.1 specification supported in clang (only one (!) clause is not

...++ and get a C++ program that runs on any Linux kernel, allowing easy distribution of a single binary? 2. should the following .so's be built with -DBUILD_SHARED_LIBS=OFF? $ ls *.so BugpointPasses.so LLVMHello.so LLVMPolly.so LLVMgold.so libLTO.so libc++.so libc++abi.so libclang.so libgomp.so libiomp5.so liblldb.so libomp.so