BitcodeTransformRule
One LLVM bitcode rewrite rule.
The rule describes the intended symbol-level change. The Gradle task decides whether the legal implementation point is before or after llvm-link.
Constructors
Properties
Null for globals, synthetic compile-unit evidence and standalone inlining rules.
Exact LLVM symbol used when a generated rule must avoid demangled glob matching.
Existing native compiler input selected by logical compile-unit identity, with its own P2 recipe.
Original compilation unit owning the definition; alternate implementations replace its matching body.
Original function location for comparison and source links; never selects a compiler input.
Explicitly initialize returned scalar fields without an incoming transfer to zero.
Functions
Stable registry identity; transform kind and lifecycle metadata deliberately do not participate.
Native compile-unit provenance, including the operational source of an alternate implementation rewrite.
True when the applied transform semantics still require source/LLVM model review.
True when a transform is intentionally unsuitable for evidence-ready analysis.
Memory models that require exact compiler member layout and parameter-name metadata.
Named parameters and fields require exact compiler types instead of the legacy untyped endpoint lowering.