Re: clang support for compiler:openmp
On Mon, Nov 07, 2016 at 10:12:59PM +0100, Matthieu Volat wrote: > On Mon, 7 Nov 2016 16:59:36 + > Brooks Daviswrote: > > > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > > Hi, > > > > > > is there a specific reason, why we do not (yet) have openmp support for > > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > > expect compiler:openmp to set > > > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > > per-port level. > > > > I talked with Baptiste about this in Belgrade. I think the best way > > forward would be to remove the OPENMP option from the llvm ports and > > alter the clang-patch-fopenmp.diff patch to use the .so from > > devel/openmp. > > > > I have a major deadline at the end of the week so it definitely won't > > happen this week. > > > > Would not that make that every clang use the llvm 3.8 libomp snapshot? It > might be useful to use later versions in some cases, but anyway, that would > be great! It would mean sticking to a single version, but I'd be pretty surprised if mixing them ended well so that's probably for the best. > It would also be awesome if base clang would be able to find omp.h and libomp > more "out of the box" once the package is installed... libomp is pretty easy once I realized I needed to hardcode the path to the .so, I'll have to see what's involved for omp.h. -- Brooks signature.asc Description: PGP signature
Re: clang support for compiler:openmp
On Mon, 7 Nov 2016 18:59:26 -0300 "Nilton Jose Rizzo"wrote: > Em Mon, 7 Nov 2016 22:12:59 +0100, Matthieu Volat escreveu > > On Mon, 7 Nov 2016 16:59:36 + > > Brooks Davis wrote: > > [...] > > I have one question about a llvm and clang ports. it's possible > port the llvm 3.9 and clang 4.0.0 with cuda support? > > I don't think we'll see that anytime soon: even if there are now some compilers that produce cuda PTX bytecode, you neeed userland and kernel code to actually compile it to native GPU code/push it/do data transfert, and only the nvidia official driver do that for now. There's some of that in the linux compatibility part of the nvidia driver, and some people managed to use it in the past, but right now, I'm not so sure. -- Mazhe pgpvVxoF50Yx7.pgp Description: OpenPGP digital signature
Re: clang support for compiler:openmp
Em Mon, 7 Nov 2016 22:12:59 +0100, Matthieu Volat escreveu > On Mon, 7 Nov 2016 16:59:36 + > Brooks Daviswrote: > > > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > > Hi, > > > > > > is there a specific reason, why we do not (yet) have openmp support for > > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > > expect compiler:openmp to set > > > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > > per-port level. > > > > I talked with Baptiste about this in Belgrade. I think the best way > > forward would be to remove the OPENMP option from the llvm ports and > > alter the clang-patch-fopenmp.diff patch to use the .so from > > devel/openmp. > > > > I have a major deadline at the end of the week so it definitely won't > > happen this week. > > > > Would not that make that every clang use the llvm 3.8 libomp > snapshot? It might be useful to use later versions in some cases, > but anyway, that would be great! > > It would also be awesome if base clang would be able to find omp.h > and libomp more "out of the box" once the package is installed... > > -- Mazhe I have one question about a llvm and clang ports. it's possible port the llvm 3.9 and clang 4.0.0 with cuda support? --- /* **Nilton José RizzoUFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clang support for compiler:openmp
On Mon, 7 Nov 2016 16:59:36 + Brooks Daviswrote: > On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote: > > Hi, > > > > is there a specific reason, why we do not (yet) have openmp support for > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd > > expect compiler:openmp to set > > > > LIB_DEPENDS+= libomp.so:devel/openmp > > > > for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a > > per-port level. > > I talked with Baptiste about this in Belgrade. I think the best way > forward would be to remove the OPENMP option from the llvm ports and > alter the clang-patch-fopenmp.diff patch to use the .so from > devel/openmp. > > I have a major deadline at the end of the week so it definitely won't > happen this week. > Would not that make that every clang use the llvm 3.8 libomp snapshot? It might be useful to use later versions in some cases, but anyway, that would be great! It would also be awesome if base clang would be able to find omp.h and libomp more "out of the box" once the package is installed... -- Mazhe pgpl3cmFmrGvS.pgp Description: OpenPGP digital signature