Hi ports --Attached is a new port, devel/openmp. OpenMP is the LLVM OpenMP stand-alone implementation.
--- pkg/DESCR: The OpenMP subproject of LLVM contains the components required to build an executable OpenMP program that are outside the compiler itself. The resulting library can be used with both clang and gcc. --- A couple notes:* I read the archives and it looks like libgomp from ports gcc was discussed some years ago but no commit ever happened. This to be honest was easier to port than trying to deal with the gcc-4.9 port. * I have no attachment to this setting COMPILER=clang. It could easily set COMPILER=gcc. I just figured since both are LLVM projects, why not. * This works with both clang and gcc-4.9. I have a port that depends on this port that builds/links with gcc-4.9. * However, gcc when given the -fopenmp flag during linking looks for a libgomp.spec file, which doesn't come with this implementation. So I just wrote one. Seamless use! * By default, the project makes libomp, libgomp, and libiomp libraries. They're all the same. The LLVM project intends for this library to be a drop-in replacement for other implementations. If and when we turn on libgomp in ports gcc, there's a flag to turn off the libgomp and libiomp creation, so both this one (as just libomp) and libgomp from gcc can live together (mostly, there would still be an issue with headers). * I am in the process of upstreaming all the patches (except patch-CMakeLists_txt): https://review.llvm.org/D34280 * The build might be broken on i386. I don't have one to test myself, but I'm relatively certain that if it does, I know where and how to fix.
Works on my amd64 with mandelbulber2 (the newer, openmp-aware version of graphics/mandelbulber that we have in ports) that I will send along once this goes in.
OK? ~Brian
openmp.tgz
Description: Binary data
