[llvm-branch-commits] [clang] [LifetimeSafety][NFC] Add field-labeled child edges to OriginNode and generalize subtree walks (PR #201510)
Utkarsh Saxena via llvm-branch-commits
llvm-branch-commits at lists.llvm.org
Thu Jun 18 07:25:29 PDT 2026
================
@@ -66,47 +66,88 @@ struct Origin {
}
};
-/// A list of origins representing levels of indirection for pointer-like types.
+/// A tree of origins representing the structure of a pointer-like or
+/// record type.
///
-/// Each node in the list contains an OriginID representing a level of
-/// indirection. The list structure captures the multi-level nature of
-/// pointer and reference types in the lifetime analysis.
+/// Each node carries an OriginID and is connected to children via labeled
+/// edges: either a pointee edge (one level of pointer/reference indirection)
+/// or a field edge (a named field of a record). Pointer-like types form a
+/// pointee chain; record types fan out via field edges.
///
/// Examples:
-/// - For `int& x`, the list has size 2:
-/// * Outer: origin for the reference storage itself (the lvalue `x`)
-/// * Inner: origin for what `x` refers to
+/// - For `int& x`, the chain has length 2:
+/// Outer: the reference storage itself (the lvalue `x`)
+/// +-pointee-> Inner: what `x` refers to
///
-/// - For `int* p`, the list has size 2:
-/// * Outer: origin for the pointer variable `p`
-/// * Inner: origin for what `p` points to
+/// - For `int* p`, the chain has length 2:
+/// Outer: the pointer variable `p`
+/// +-pointee-> Inner: what `p` points to
///
-/// - For `View v` (where View is gsl::Pointer), the list has size 2:
-/// * Outer: origin for the view object itself
-/// * Inner: origin for what the view refers to
+/// - For `View v` (View is gsl::Pointer), the chain has length 2:
+/// Outer: the view object itself
+/// +-pointee-> Inner: what the view refers to
///
-/// - For `int** pp`, the list has size 3:
-/// * Outer: origin for `pp` itself
-/// * Inner: origin for `*pp` (what `pp` points to)
-/// * Inner->Inner: origin for `**pp` (what `*pp` points to)
+/// - For `int** pp`, the chain has length 3:
+/// Outer: `pp` itself
+/// +-pointee-> Inner: `*pp` (what `pp` points to)
+/// +-pointee-> Inner->Inner: `**pp` (what `*pp` points to)
///
-/// The list structure enables the analysis to track how loans flow through
-/// different levels of indirection when assignments and dereferences occur.
+/// - For `struct S { View a; Inner b; }` (with `struct Inner { View c; }`),
+/// the node fans out into a tree, one `field` edge per field with origins:
+/// O_s: the record `s` (holds no loans directly)
+/// +-field a-> O_a: what the `View` field `s.a` refers to
+/// +-field b-> O_b: the record `s.b` (holds no loans directly)
+/// +-field c-> O_c: what the `View` field `s.b.c` refers to
///
-/// TODO: Currently list-shaped (each node has at most one pointee child).
-/// Will become tree-shaped once field children are added to support
-/// origin trees for records whose fields have origins.
+/// The structure enables the analysis to track how loans flow through
+/// levels of indirection and across record fields when assignments and
+/// dereferences occur.
class OriginNode {
public:
+ /// A labeled edge from this node to a child. The label distinguishes how
+ /// the child is reached: a null `FD` means a pointee edge (one level of
+ /// pointer/reference indirection); a non-null `FD` means a field edge
+ /// (the named field of a record). Putting the label on the edge lets
+ /// one child node play different roles per parent. For example, the subtree
+ /// for `s`'s `v` field is reached from `s`'s record (FD=v) and from
+ /// the lvalue outer built for the MemberExpr `s.v` (FD=null).
----------------
usx95 wrote:
nit: formatting to make this easier to follow:
```
/// A labeled edge from this node to a child. The `FD` label determines the
/// edge type:
/// - null `FD`: a pointee edge (one level of pointer/reference indirection)
/// - non-null `FD`: a field edge (the named field of a record type)
///
/// The label allows the same child subtree to be reachable via different
/// relationships. For example, the subtree for field `v` in `s.v` can be
/// reached both
/// (1) as a field child from `s`'s node (with FD=v), and
/// (2) as a pointee child from the lvalue node for `s.v` (with FD=null).
```
https://github.com/llvm/llvm-project/pull/201510
More information about the llvm-branch-commits
mailing list