The LLVM Project is a collection of modular and reusable compiler and
toolchain technologies.
This port includes Clang (a C/C++/Objective-C compiler), LLD (a linker),
LLDB (a debugger), an OpenMP runtime library, and the LLVM infrastructure
these are built on.
===> The following configuration options are available for llvm19-19.1.7_5:
BE_AMDGPU=on: AMD GPU backend (required by mesa)
BE_WASM=on: WebAssembly backend (required by firefox via wasi)
CLANG=on: Build clang
COMPILER_RT=on: Sanitizer libraries
DOCS=on: Build and/or install documentation
EXTRAS=on: Extra clang tools
FLANG=off: Flang FORTRAN compiler
LIT=on: Install lit and FileCheck test tools
LLD=on: Install lld, the LLVM linker
LLDB=on: Install lldb, the LLVM debugger
MLIR=on: Multi-Level Intermediate Representation
OPENMP=on: Install libomp, the LLVM OpenMP runtime library
POLLY=on: Polyhedral loop and data-locality optimizer
PYCLANG=on: Install python bindings to libclang
STATIC_LIBS=on: Install static libraries (does not effect sanitizers)
====> Options available for the single BACKENDS: you have to select exactly one of them
BE_FREEBSD=off: Backends for FreeBSD architectures
BE_NATIVE=off: Backend(s) for this architecture (X86)
BE_STANDARD=on: All non-experimental backends
===> Use 'make config' to modify these settings
devel/llvm19: fix build on 15.1, 14.4
This patch only works on systems with the libc++ from LLVM 21 so bound
its application appropriatly.
PR: 299993, 296203
Fixes: 6a0f728d9cd8 ("devel/llvm19: fix build with flang and libc++ 21")
devel/llvm[14-22]: backport powerpc64le patch from CURRENT
Since 16.0, powerpc64le switches to IEEE long double binary128.
This set of patches backports the change from CURRENT.
LLVM 12 and 13 are omitted, because binary128 handling in those
versions is not finished.
devel/llvm??: remove libxml2 discovery
In commit af979dd126ff4 the dependency on libxml2 was removed. But
libxml2 was still found for LLDB and used if it was present at configure
time.
PR: 295076
Submitted by: laurent
devel/llvm??: Add Mips back to standard backends
I'd forgotten that STANDARD_BACKENDS is includes _FREEBSD_BACKENDS so
Mips dropped out of the list when it was removed from _FREEBSD_BACKENDS.
PR: 295111
Fixes: 2a7c0561200c ("all: drop support for FreeBSD 13, mips and risc64sf")
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
devel/llvm{19,20,21,22}: don't set LLVM_ENABLE_TERMINFO=OFF
LLVM dropped use of TERMINFO prior to LLVM 19 so stop trying to disable
it.
Sponsored by: DARPA, AFRL
devel/llvm19: don't build gold plugin when disabled
Disabling the GOLD option didn't actually disable building the plugin,
it just didn't install it in the package. Actually stop traversing into
the directory when the option disabled so we don't end up needing
devel/binutils.
PR: 291247
Sponsored by: DARPA, AFRL
devel/llvm{19,20,21}: fix build on riscv64
=======================<phase: check-sanity >============================
====> You must select one and only one option from the BACKENDS single
=====> No option was selected (and one must be)
Approved by: portmgr (build fix blanket)
MFH: 2025Q3
python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
(Only the first 15 lines of the commit message are shown above )
devel/llvm19: reenable AMDGPU and WASM on i386 by default
This is needed (among other reasons) to support wine because wine is
mostly 32-bit.
Requested by: manu
Sponsored by: DARPA, AFRL
devel/llvm19: Fix !CLANG plist and OPENMP
llvm-debuginfo-analyzer isn't part of Clang, but was matched by the
overly broad pattern `-analyzer`. [0]
Fix USE_LDCONFIG for OPENMP. [1]
Reported by: jrtc27 [0], tijl [1]
Sponsored by: DARPA, AFRL
devel/llvm*: flip LICENSE_FILE_BSD3CLAUSE setting [NFC]
The location of this license file moved in LLVM 16. Since I'm doing
cleanup in this area and the split of ports is about 50/50, switch to
setting the old location in the older ports so the newer ports set fewer
variables.
Sponsored by: DARPA, AFRL
devel/llvm*: LICENSE_DIR simplification
WRKSRC moved to the top of the source tree with llvm12. As a result,
LICENSE_DIR became ${WRKSRC}/llvm. Given that llvm11 the only port that
wasn't setting LICENSE_DIR, flip the script and default to
${WRKSRC}/llvm with llvm11 overriding.
Sponsored by: DARPA, AFRL
devel/llvm*: Always define LLVM2 license [NFC]
All LLVM ports in the tree use the Apache License 2.0 with LLVM
Exceptions license so cerntralize the definition.
Sponsored by: DARPA, AFRL
devel/llvm[789]: restore arm_bf16.h to ARM backend
arm_bf16.h is generated for both armv7 and aarch64 so move it back to
ARM. We don't support AArch64 without ARM so we can just move it and
not need to worry about duplicate supression (I'd previously fixed the
issue in llvm19 in a more complicated manner so this change removes the
duplicate supression and documents why it's not needed.)
PR: 281179
Reported by: Mark Millard
devel/llvm19: update to 19.1.0-rc4
arm_bf16.h is installed by the ARM backend as well as AArch64 so handle
that.
Patch out upstream 6d7e428df611 which traded a false negative for a
false positive when compiling compiler-rt for i386.
Fix default options for 32-bit powerpc arches.
PR: 281179
devel/llvm19: prune build on 32-bit archs
Given trends in compiler resource use, it is incresingly implausible to
consider cross-development from a 32-bit system. As such, stop spending
time building LLVM bits are are vinishingly unlikely to be used on
32-bit systems.
Default to BE_NATIVE (no cross build support) on 32-bit plaforms.
Disable BE_AMDGPU and BE_WASM as well. BE_AMDGPU consumes enormous
amounts of memory. BE_WASM is less problematic, but no one has stood up
to say they need it so turn it off for now.
Completely disable MLIR and POLLY on 32-bit. Just building MLIR fails
routinly on armv7 and there aren't a lot of direct users (it's used by
FLANG, but FLANG is 64-bit only). Polly is pretty niche and adds quite
a bit of build time.
Sponsored by: DARPA, AFRL
Differential Revision: https://reviews.freebsd.org/D46239
