ports/devel/llvm15, branch 14.3-eol

devel/llvm[14-22]: backport powerpc64le patch from CURRENT

2026-06-21T20:05:19Z

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

2026-05-22T11:36:23Z

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??: Bump PORTREVISION for 4fc6c5e1c9a4

2026-05-13T13:47:05Z

PR: 295111

devel/llvm??: Add Mips back to standard backends

2026-05-11T09:29:31Z

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

2026-05-07T21:47:29Z

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/llvm15: fix build with clang 21

2026-01-14T17:36:44Z

Recent versions of clang complain about explicit copy constructors, leading to errors similar to: /wrkdirs/usr/ports/devel/llvm15/work-default/llvm-project-15.0.7.src/llvm/tools/sancov/sancov.cpp:532:44: error: chosen constructor is explicit in copy-initialization 532 | return SpecialCaseList::createOrDie({{ClBlacklist}}, | ^~~~~~~~~~~~~ /usr/include/c++/v1/string:1153:64: note: explicit constructor declared here 1153 | _LIBCPP_HIDE_FROM_ABI _LIBCPP_CONSTEXPR_SINCE_CXX20 explicit basic_string(const _Tp& __t) { | ^ /usr/include/c++/v1/__vector/vector.h:276:91: note: passing argument to parameter '__il' here 276 | _LIBCPP_CONSTEXPR_SINCE_CXX20 _LIBCPP_HIDE_FROM_ABI vector(initializer_list __il) { | ^ /wrkdirs/usr/ports/devel/llvm15/work-default/llvm-project-15.0.7.src/llvm/tools/sancov/sancov.cpp:535:42: error: chosen constructor is explicit in copy-initialization 535 | return SpecialCaseList::createOrDie({{ClIgnorelist}}, | ^~~~~~~~~~~~~~ /usr/include/c++/v1/string:1153:64: note: explicit constructor declared here 1153 | _LIBCPP_HIDE_FROM_ABI _LIBCPP_CONSTEXPR_SINCE_CXX20 explicit basic_string(const _Tp& __t) { | ^ /usr/include/c++/v1/__vector/vector.h:276:91: note: passing argument to parameter '__il' here 276 | _LIBCPP_CONSTEXPR_SINCE_CXX20 _LIBCPP_HIDE_FROM_ABI vector(initializer_list __il) { | ^ In this case, `ClBlacklist` and `ClIgnoreList` are instances of `cl::opt`, not a `std::string` as expected. Use `getValue()` to get the actual `std::string` values. PR: 292111 Approved by: brooks (maintainer) MFH: 2026Q1

devel/llvm1[4567]: keep backport patches local

2026-01-14T15:09:14Z

The patches generated by adding .patch to a github commit URL are unstable and the output of some of them changed recently. It's concivable this will be fixed, but they probably won't make any long term guarantees so store the patches in the ports tree instead of downloading them. PR: 292291 MFH: 2026Q1 Sponsored by: DARPA, AFRL See also: https://github.com/orgs/community/discussions/184094

devel/llvm15: don't build gold plugin when disabled

2025-12-09T16:05:34Z

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

python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc

2025-06-19T20:28:47Z

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. Introduce PYTHON_SOABI to align with PEP 3149's specification of a tag, which consists of implementation name, shorthand version and any ABI flags present (this and PYTHON_TAG are identical without ABI flags). This is meant for compiled extension module objects and other files that depend on a specific Python ABI for the same version. Add documentation for these variables that our PYTHON_EXT_SUFFIX never had. PR: 274671 Event: Kitchener-Waterloo Hackathon 202506

devel/llvm15: fix backport of llvm19 fixes

2025-03-14T00:56:37Z

There was a missing line in the patch causing part of it to be ignored. PR: 285195 Submitted by: milios@ccsys.com Fixes: ce2f720d96cd devel/llvm15: backport flang fixes for llvm19