[SSAF] Add SourcePassAnalysis framework
SourcePassAnalysis is for analyses/actions to be performed in a second
pass on source code, after the SSAF whole-program analysis.
SourcePassAnalysis is defined as an ASTConsumer abstraction that
depends on a whole-program analysis result.
This commit adds:
- SourcePassAnalysis base classes
- SourcePassAnalysis registry
- unit test for registry
rdar://175802731
[lldb] Change TestPublicAPIHeaders.py to only build when the target architecture matches the host's (#193848)
This test requires that LLDB.framework be built the same architecture as
the test binary (effectively). There's no way to specify that in our
testing logic currently, so let's just mark this test as arm64 only for
now.
---------
Co-authored-by: Jonas Devlieghere <jonas at devlieghere.com>
[lldb] Remove verbose DWARF spec comments from evaluator (NFC) (#195140)
Most labels in DWARFExpression::Evaluate have a 3-10 line
OPCODE/OPERANDS/DESCRIPTION block copied from the DWARF specification.
My assumption is that anyone editing this code should be consulting the
latest version of the spec, which is the (only) source of truth. This
approach doesn't scale, create the opportunity for subtle bugs and makes
the code harder to read.
Anything LLDB specific (i.e. that's not part of the spec) is preserved.
InstCombine: Don't read first argument of llvm.ptrauth.* call argument until checking intrinsic ID.
If llvm.ptrauth.auth or llvm.ptrauth.resign is called on the result of
a call with no arguments InstCombine will hit an assertion failure due
to reading the non-existent first argument. Fix it.
Assisted-by: gemini (wrote test)
Reviewers: nikic, fmayer
Pull Request: https://github.com/llvm/llvm-project/pull/195195
[clang][modules] Make -fmodules-decluse work on the public/private pair of modules (#192585)
Previously, it would only check the main module.
Now, if the main module is a private module (foo_Private), it will also check the public module.
[lldb] Extract DW_OP_fbreg and DW_OP_call_frame_cfa evaluation (NFC) (#195143)
Both case bodies had several levels of nested if/else validating the
execution context and frame before doing the real work. Invert the
checks and move the bodies to static helpers alongside
Evaluate_DW_OP_piece, matching the pattern already used for
Evaluate_DW_OP_deref_size and Evaluate_DW_OP_entry_value.
[MLIR][Vector] Add unrolling support for bitcast, interleave, and deinterleave ops (#194513)
This patch implements VectorUnrollOpInterface and unrolling patterns for
vector bitcast,
interleave, and deinterleave operations.
---------
Co-authored-by: Claude Sonnet 4.5 <noreply at anthropic.com>
[dsymutil] Fix ODR type uniquing for -gsimple-template-names (#194501) (#195174)
With -gsimple-template-names (now the default on macOS with deployment
target >= 26), template types like vector<int> and vector<float> both
get DW_AT_name("vector") in DWARF, with template parameters encoded only
as DW_TAG_template_type_parameter children.
Previously, dsymutil used only DW_AT_name for ODR type uniquing, causing
different template specializations to collide. This PR fixes that by
reconstructing template parameter information from child DIEs when the
type name does not already contain template parameters.
The reconstructed name is used only for uniquing and not emitted into
the output DWARF. The parallel DWARF linker already handled this
correctly via SyntheticTypeNameBuilder.
This reland removes an overly strict assertion when clang emits
DW_TAG_subprogram DIEs with a demangled template-like DW_AT_name (e.g.
foo<int>) but no DW_AT_linkage_name. The surrounding logic already
[5 lines not shown]
[lldb] Extract DW_OP_form_tls_address evaluation (NFC) (#195144)
The DW_OP_form_tls_address / DW_OP_GNU_push_tls_address case had
multiple nested null-checks and a branching error message before a few
lines of real work. Move it to a static helper.
[offload] record-replay: only check user-provided grid sizes
The plugins sometimes change what the user provided for num_threads or
num_teams and choose different values for the actual launch. This should
not lead to errors in the replay mechanism. The original clause values
should only be checked if the user specified new values for replay
explicitly.
[mlir] Interface-ify updating starting positions on vector.transfer_*
This commit adds methods to VectorTransferOpInterface that allow
transfer operations to be queried for whether their base memref (or
tensor) and permutation map can be updated in some particular way and
then for performing this update. This is part of a series of changes
designed to make passes like fold-memref-alias-ops more generic,
allowing downstream operations, like IREE's transfer_gather, to
participate in them without needing to duplicate patterns.
In order to test this new method, migrate FoldMemrefAliasOps to use
these methods to fold memref.subview, memref.expand_shape,and
memref.collapse_shape into tranfer_read and transfer_write.
AI note: the tranfer_read / transfer_write patterns, which are taken
from a previous PR, were written with Claude 4.5.
[VPlan] Remove recipe tracking in VPRecipeBuilder. (NFC) (#195181)
Remove Instruction-to-recipe mapping from RecipeBuilder. The only
remaining user is createInterleaveGroups, where we can easily collect
the mapping.
Add the ability to pass a parent to ValueObjectMemory::Create. (#195155)
Also move the equivalent helper function from ValueObjectConstResult to
ValueObject.h where it more properly belongs.
This patch is necessary if one were to use ValueObjectMemory for a
synthetic child. There aren't any current uses of this sort in lldb,
though there are on the swift fork.
Update clang/include/clang/ScalableStaticAnalysisFramework/Analyses/PointerFlow/PointerFlowAnalysis.h
Co-authored-by: Jan Korous <jkorous at apple.com>
