Date: Tue, 30 Aug 2016 12:39:04 -0500 From: "Eric A. Borisch" <eborisch@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Benchmarks results for FreeBSD 11 Message-ID: <CAASnNnqGFJ9bwZ-k3CrobRaPWcOFnxEQJ=crnV-BGAQ_REtZUA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
FWIW, in MacPorts, we patch clang such that it can find the (MacPorts provided) libomp headers and library. This lets -fopenmp "just work," and configure scripts can do their job. The libomp headers and lib in dedicated sub-directories to minimize the impact of -fopenmp adding them to the include and link paths. It is a fairly minor patch, and shouldn't (tm) have any impact on clang executions without an openmp flag: https://trac.macports.org/browser/trunk/dports/lang/llvm-3.8/files/openmp-locations.patch To get a simple OpenMP test script to compile on FreeBSD, I currently need to pass (note I'm not the one using -lm): clang38 -fopenmp -o test test.c -L /usr/local/llvm38/lib -lm instead of (~ what configure will try) clang38 -fopenmp -o test test.c (11.0RC2 w/ llvm38 installed via pkg) I'd love to see base include llvm's OpenMP support, but failing that, the one from ports should be made to work as configure scripts expect. And who knows, if it is there, maybe some items in base will start to use it. We've got a chicken-and-egg problem right now. - Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAASnNnqGFJ9bwZ-k3CrobRaPWcOFnxEQJ=crnV-BGAQ_REtZUA>