3 ms·

I wonder how they're getting around the issue of LLVM's lack of OpenMP support. I'm sure there are atleast a few modules in FreeBSD that utilize OpenMP. I too w

by rwbt 13y ago

I wonder how they're getting around the issue of LLVM's lack of OpenMP support. I'm sure there are atleast a few modules in FreeBSD that utilize OpenMP. I too want to switch from GCC to LLVM/Clang but can't right now since LLVM doesn't support OpenMP yet.

sanxiyn 13y ago
Can't those modules simply depend on GCC? FreeBSD is no longer building GCC by default. You can still build GCC as an option.
jevinskie 13y ago
You won't have to wait for long! Initial patches have already been accepted as of August 27th. http://permalink.gmane.org/gmane.comp.compilers.clang.devel/31340 http://permalink.gmane.org/gmane.comp.compilers.clang.devel/... http://clang-omp.github.io/ http://clang-omp.github.io/
- sanxiyn 13y ago
  Your link does not show any evidence of this being "accepted".
emaste 13y ago
GCC is still available in the ports tree, and specific ports that depend on being built by GCC (for whatever reason) specify that requirement. This change affects only the GCC that shipped in the FreeBSD base system.
4ad 13y ago
> I'm sure there are atleast a few modules in FreeBSD that utilize OpenMP. Nothing in the base system uses OpenMP. I find your assumption extremely bizarre (and scary). The kernel and the base system is the kind of software OpenMP would not be of any use. In fact, the base system is not even written in C++, but C; the only C++ components are groff and llvm (go figure). $ lsr /usr/src/ | egrep '\.(c|cpp|h|hpp)$' | xargs egrep '^[[:space:]]*#[[:space:]]*pragma[[:space:]]+omp' | grep -v gcc | wc -l 0 Non-base software from the ports systems uses its own compiler. The system compiler is used for compiling FreeBSD.
- Malus 13y ago
  You forgot devd, which is also written in C++: http://svnweb.freebsd.org/base/head/sbin/devd/ http://svnweb.freebsd.org/base/head/sbin/devd/ By default, ports use the system compiler unless it is specifically overridden in the port's Makefile (e.g. USE_GCC=any).
- X-Istence 13y ago
  Do note that .cc is also a valid C++ extension.

by rwbt 13y ago

sanxiyn 13y ago

Can't those modules simply depend on GCC? FreeBSD is no longer building GCC by default. You can still build GCC as an option.

jevinskie 13y ago

You won't have to wait for long! Initial patches have already been accepted as of August 27th. http://permalink.gmane.org/gmane.comp.compilers.clang.devel/31340 http://permalink.gmane.org/gmane.comp.compilers.clang.devel/... http://clang-omp.github.io/ http://clang-omp.github.io/

sanxiyn 13y ago
Your link does not show any evidence of this being "accepted".

emaste 13y ago

GCC is still available in the ports tree, and specific ports that depend on being built by GCC (for whatever reason) specify that requirement. This change affects only the GCC that shipped in the FreeBSD base system.

4ad 13y ago

> I'm sure there are atleast a few modules in FreeBSD that utilize OpenMP. Nothing in the base system uses OpenMP. I find your assumption extremely bizarre (and scary). The kernel and the base system is the kind of software OpenMP would not be of any use. In fact, the base system is not even written in C++, but C; the only C++ components are groff and llvm (go figure). $ lsr /usr/src/ | egrep '\.(c|cpp|h|hpp)$' | xargs egrep '^[[:space:]]*#[[:space:]]*pragma[[:space:]]+omp' | grep -v gcc | wc -l 0 Non-base software from the ports systems uses its own compiler. The system compiler is used for compiling FreeBSD.

Malus 13y ago
You forgot devd, which is also written in C++: http://svnweb.freebsd.org/base/head/sbin/devd/ http://svnweb.freebsd.org/base/head/sbin/devd/ By default, ports use the system compiler unless it is specifically overridden in the port's Makefile (e.g. USE_GCC=any).
X-Istence 13y ago
Do note that .cc is also a valid C++ extension.