AMDGPU: Use LastSubtargetCache in getSubtargetImpl (#242560)
Reuse the last subtarget for functions with the same function
attribute set and module, or the same subtarget relevant attributes
and module flags, instead of building the subtarget key. This is
faster and works towards all targets using a common pattern.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[lldb][test] Fix expected message in TestPtrAuth.py (#243934)
During the review #242399, I updated the error message, but didn't
update the test. It also fix format error.
[CodeGen] Remove more legacy option spellings that have no in-tree use (#243948)
PR #243179 renamed these options and kept the old spellings as aliases.
Nothing in the tree uses the old spellings, so remove them now.
[ProfCheck] Mark new VP metadata tests as unsupported (#243947)
These fail under profcheck as profcheck automatically runs prof-inject
which makes one of the verification cases fail.
[llvm-profgen] Cache and explain the pre-inliner hot threshold
Compute the hot threshold once in the CSPreInliner constructor instead
of recomputing it for every caller. The input summary stays fixed for
the pre-inliner run.
Document why the ICP checks keep the contextless summary. The loader's
nested summary depends on the inline decisions and can give a lower
threshold. Using a lower estimate could let more indirect targets spend
the caller's inline size budget, leaving less room for other callees.
Rejected contexts instead follow the existing base-profile merge path.
The loader continues to apply its own hotness check.
Clarify nearby comments and diagnostics so a pre-inliner rejection is
not presented as an exact prediction of the loader. Add coverage for an
explicit hot-count override. Profile selection is unchanged.
Assisted-by: GPT-6 Astra
[llvm-profgen] Respect the sample loader's indirect-call promotion limits
The CS pre-inliner can plan to inline a target that the sample loader
will not promote. Keep rejected contexts in the callee's base profile
instead of spending the caller's inline budget on them.
Read the loader's hotness, initial exemption, and maximum-promotion
options. Account for call-target counts being replaced by nested head
estimates as targets are accepted. Leave the compiler thresholds intact.
Apply the gate only to sites with an indirect-call pseudo probe. Collect
that evidence during the existing decoder pass, including functions and
inlinees skipped by the sample GUID filter. Add a decoder callback test
and profile tests for the promotion limits and call-probe checks.
This follows the compiler-side recovery change, which also handles hot
contexts already nested in existing generated profiles.
Assisted-by: GPT-6 Astra
[CodeGen] Remove legacy option spellings that have no in-tree use (#243946)
PR #243746 renamed these options and kept the old spellings as aliases
(convenient to downstream users that might use them). Nothing in the
tree uses the old spellings, so remove them now.
[SampleProfile] Recover indirect targets after iterative inlining
An indirect fallback survives when a target is promoted and inlined. Recording its hottest target on every scan can therefore merge samples from an inline copy into the standalone function. Recording only one target also loses samples for other targets that stay out of line.
Collect recovery candidates from the calls that remain after inlining finishes. Use the existing promotion history to exclude promoted targets from the fallback, and recover promoted direct calls separately if they did not inline. This also handles promotion without a successful inline or another iteration.
[lldb] Fix a crash in SBTypeSynthetic::IsEqualTo (#243932)
Comparing a valid SBTypeSynthetic to an invalid one dereferenced a null
pointer.
Assisted-by: Claude
[SPIR-V] Drop type incompatible attributes after aggregate signature rewrite (#242704)
Retyped functions and calls that kept attributes like nofpclass on i32,
which are rejected by verifier
[CodeGen] Declare command line options of more passes in TableGen (#243746)
Renames, with the old spellings kept as aliases:
* Negative to positive: -no-stack-coloring, -no-stack-slot-sharing,
-disable-phi-elim-edge-splitting and -no-phi-elim-live-out-early-exit
become -stack-coloring, -stack-slot-sharing, -phi-elim-edge-splitting
and -phi-elim-live-out-early-exit.
* Drop enable-: -enable-shrink-wrap, -enable-shrink-wrap-region-split
and -enable-tail-merge become -shrink-wrap, -shrink-wrap-region-split
and -tail-merge, and -enable-spill-copy-elim becomes
-mcp-spill-copy-elim.
* Add the pass prefix: the MachineLICM options gain machine-licm-, and
-aggressive-machine-cse, -csuses-threshold, -dataflow-edge-limit and
-protect-from-escaped-allocas become -machine-cse-aggressive,
-machine-cse-csuses-threshold, -twoaddr-dataflow-edge-limit and
-stackcoloring-protect-from-escaped-allocas.
Other changes:
[6 lines not shown]
[libc++][docs] Make status colors readable in Furo dark mode
The status table cell colors are light pastels. Furo's dark theme uses light
text, so cells such as "Complete" were unreadable. Use darker backgrounds
for the explicit dark theme and for the automatic theme when the browser
prefers a dark color scheme.
LLM-aided