style.9: Avoid C++ keywords
Headers may be included by C++ code, and sometimes we might like to
use exinst code as C++. Encourage authors to avoid C++ keywords as
identifiers.
Reviewed by: des, imp (earlier version)
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D61767
[lldb] Remove ConstString from DynamicRegisterInfo (#243644)
RegisterInfo and RegisterSet both have `const char *` values. In many
cases, they are backed by static data and so their lifetime is
guaranteed. The one case where this is not true is DynamicRegisterInfo.
DynamicRegisterInfo produces RegisterInfo and RegisterSet objects for
register information that lldb is not aware of ahead of time. Currently
it stores strings in the ConstString pool to guarantee their lifetimes
for the remainder of lldb's run time. As a part of removing ConstString
from LLDB in general, this change ties those strings to the lifetime of
the DynamicRegisterInfo itself.
There are a few cases where RegisterInfo objects are pulled out of
DynamicRegisterInfo or a DynamicRegisterInfo object is copied. Those
cases are handled carefully, sometimes with ConstString, to make sure we
are not producing dangling pointers. Future changes will fix them.
[libLTO] Apply late -mllvm options to the target options (#244090)
lto_codegen_debug_options and lto_codegen_debug_options_array only
record the options. They are parsed when the first output is produced,
but the target options, including the MC options, are read from the
library options when the generator is created. Options that ld64 passes
with -mllvm, such as -macho-relocatable-dwarf or
-nozero-initialized-in-bss, were parsed and then ignored.
Read the target options again after the late options are parsed.
lto_set_debug_options and thinlto_debug_options parse before the
generator is created and are unchanged.
[InstCombine] Check the select type in the usub.sat sign mask fold
`foldICmpUSubSatWithAndForMostSignificantBitCmp` replaces a select with an
`and` that has the type of the `usub.sat` operands. When the select has a
different type, the replacement hits the assertion "replaceAllUses of value
with new value of different type!".
This PR skips the fold in that case.
This PR was assisted by AI but I reviewed all the changes.
[VPlan] Remove ExtractLastPart when unrolling with UF 1. (NFC) (#244304)
ExtractLastPart is meant to be removed by unrolling, but with UF 1
unrollByUF returned early and left it in place; simplifyRecipe folded it
later, after replicateByVF. Remove it in unrollByUF's cleanup for any UF
instead. Nothing creates ExtractLastPart after unrolling since the
previous commit, so the fold in simplifyRecipe is no longer needed.
This is needed to lower lane extracts of replicated values directly in
replicateByVF in a follow-up. The generated IR does not change.
PR: https://github.com/llvm/llvm-project/pull/244304
[NFC] Use std::optional<uint64_t> for AAMDNodes::extendTo (#244301)
Non-functional change to simplify the helper functions for AA metadata
extension to different sizes.
This was requested in review of #240267.
Assisted by Claude
2026Q4: PHP security updates from FreeBSD 2026Q4 8be526f83c15
Composed from DeltaPorts afd0c728e3f on FreeBSD 2026Q4 8be526f83c15,
with DPorts master (e2f31ebea3a) as lock repo. Only lang/php82-85
change; the rest of the tree stays as it was.
- lang/php82 8.2.36 (c926a44cb3dc), lang/php83 8.3.37 (d0e200a74bde),
lang/php84 8.4.28 (abdff97af6e6), lang/php85 8.5.13 (a7d1019ac0a3)
- 4 to 7 critical, 4 high and 4 to 6 medium advisories per branch.
The critical ones are remote code execution through session
handling and the timezone cache (CVE-2026-115560, CVE-2026-126714,
CVE-2026-129481, CVE-2026-129496), PHP-FPM request smuggling
(CVE-2026-129289) and, in 8.5 only, two engine use-after-frees
(CVE-2026-129474, CVE-2026-129182)
- The bundled extensions and www/mod_php8x are slave ports of these
and take the new version with them.
PHP_API_VERSION and ZEND_MODULE_API_NO stay the same in each branch,
and the installed headers keep their struct layouts, so PECL
[4 lines not shown]
[lldb] Define SB API special members out of line (#241980)
When liblldb is built with clang-cl and `/Zc:dllexportInlines-`, inline
members are not exported from liblldb.dll. A client compiled without the
flag then fails to link.
This changes the SB API to declare and define out of line copy
constructors, copy assignment and destructors, following the guidance in
`docs/resources/sbapi.md`:
> All the SB API classes are non-virtual, single inheritance classes.
> They should only include SBDefines.h or other SB headers as needed.
> There should be no inlined method implementations in the header
> files, they should all be in the implementation files. And there
> should be no direct ivar access.
The effort to build LLVM as a dylib is tracked in #109483.
[CIR] Add handling for base subobject alignment (#244018)
While working on a previous update to CIR's record alignment handling, I
came across a corner case where we weren't recording user-specified
alignment for a base subobject and also didn't have enough information
to reconstruct the alignment during calling convention lowering. This
change fixes that problem.
Assisted-by: Cursor / Grok 4.7
[Clang][Sema] Add fortify warnings for memccpy, memset_explicit, and explicit_bzero (#243629)
Teach `-Wfortify-source` in `Sema::checkFortifiedBuiltinMemoryFunction`
to diagnose destination buffer overflows/size mismatches for:
- `memccpy` (`warn_fortify_source_size_mismatch`, since copying stops if
the stop byte is found in the source buffer before reaching `n`,
analogous to `strncpy`/`stpncpy`/`strlcpy`)
- `memset_explicit` (`LibBuiltin<"string.h">` from C23,
`warn_fortify_source_overflow`)
- `explicit_bzero` (`GNULibBuiltin<"string.h">`,
`warn_fortify_source_overflow`)
Also pass explicit builtin parameter indices rather than
`TheCall->getNumArgs() - 1` to
`Checker.ComputeExplicitObjectSizeArgument` so
`__attribute__((diagnose_as_builtin(...)))` wrappers with extra
parameters translate the size argument index properly.
Part of #142230
Assisted-by: Gemini
EliminateAvailableExternally: Preserve the function analysis manager proxy (#244023)
Previously all cached function analyses were cleared When only
deleting function bodies, clear the analyses of those functions and
preserve the proxy.
CTMark instructions:u geomean: O3 -0.02% (kimwitu++ -0.12%, tramp3d-v4
-0.12%), ThinLTO -0.01%.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[CIR] Rerun the CIR pipeline on ClangIR input and add -emit-cir=pristine (#243679)
This follows the RFC accepted by the Clang Area Team as `-cc1
-emit-cir=keyword`:
https://discourse.llvm.org/t/rfc-clangir-making-cir-pipeline-boundaries-first-class-driver-artifacts/90998
So far, `.cir` input to cc1 skipped the CIR-to-CIR pipeline, because the
lowering passes were not safe to rerun. With #237433, #237395, #237376,
#237413 and #239847 merged (it is likely that I am forgetting some
here). Rerunning them on their own output now leaves it unchanged, so
ClangIR input runs the full pipeline like source input.
The trade-off here is compilation time, you may end up running the
pipeline twice. I personally am ok with that as any user of
this option is responsible to set their policy.
`-emit-cir=pristine` emits CIRGen's output before any ClangIR pass runs,
which is the point before target lowering that the RFC asked for.
[16 lines not shown]
[Clang][OpenMP] Fix crash on an `omp allocate` local in unreachable code (#242302)
Fixes #140336
CodeGen visits declarations even after the insertion point has been
cleared, but the `omp allocate` path still emitted the `__kmpc_alloc`
call there. For a declaration nothing can reach, such as a `switch` body
before its first `case`, the call ended up outside any basic block and
the verifier rejected the module.
Both allocation hooks now return early when there is no insertion point
and the variable keeps its plain alloca. Jumping into the scope of such
a variable is now an error, as for `__attribute__((cleanup))` and as GCC
does (Here I follow the GCC behavior, if you prefer we could change the
approach in that case): the allocation would be skipped but the
`__kmpc_free` at scope exit would still run.
AI assisted!
www/rustfs: Update 1.0.4 to 1.0.5
Stop forcing fat LTO (WITHOUT_LTO), so the build uses the thin LTO from
upstream's release profile.
Make the data directory modifiable with the RUSTFS_DBDIR variable.
Mark BROKEN on i386: rustc runs out of memory.
Changelog: https://github.com/rustfs/rustfs/releases/tag/1.0.5
Reported by: Mickael Maillot <mmaillot at secuserve.com> (memory)
Reported by: pkg-fallout (i386)
Suggested by: otis (RUSTFS_DBDIR)
Reviewed by: otis
Approved by: jrm (mentor)
Differential Revision: https://reviews.freebsd.org/D61470
[AMDGPU][AsmParser] Require a comma between dfmt and nfmt (#241328)
PR46403 says that the MTBUF syntax expects dfmt and nfmt to be separated
by a comma. Nothing required supporting the comma as optional: dfmt and
nfmt were always ordinary operands. They were separate operands before
35484c9d5024, and the printer has always printed them as 'dfmt:N,
nfmt:M'.
Another step towards checks for correct use of commas between operands.
Assisted-By: Claude