llvm-project.git/llvm/test/DebugInfo/KeyInstructions, branch users/nico/python-2

[KeyInstr] Fully support mixed key/non-key inlining modes (#144103)

2025-06-30T08:56:56+00:00

Patch 3/4 adding bitcode support, though the final patch doesn't depend on this
one.

Prior to this patch, a Key Instructions function inlined into a
Not-Key-Instructions function fell back to Not-Key-Instructions handling.

In order to fully support inlining mixed modes we need to run
`computeKeyInstructions` (in case there's a Key Instructions scope) and
`findForceIsStmtInstrs` (in case there's a Not-Key-Instructions scope) on all
functions. This has a slight performance cost for all configurations - see PR
for details.

[KeyInstr] Use DISubprogram's is-key-instructions-on flag at DWARF emission (#144104)

2025-06-30T07:06:22+00:00

Patch 2/4 adding bitcode support.

A non-key-instructions function inlined into a key-instructions function uses
non-key-instructions is_stmt placement (without `findForceIsStmtInstrs`).

A key-instructions function inlined into a non-key-instructions function
currently results in falling back to non-key-instructions for the inlined scope
too.

Both of these concessions (not using `findForceIsStmtInstrs` in the 1st case,
and not using Key Instructions for the inlined scope in the 2nd) are for
performance reasons; to do the right thing we'd need to run both
`findForceIsStmtInstrs` and `computeKeyInstructions` - in case that's
controversial I've got a separate PR for that: PR 144103.

[KeyInstr] Add DISubprogram::keyInstructions bit (#144107)

2025-06-30T07:01:55+00:00

Patch 1/4 adding bitcode support.

Store whether or not a function is using Key Instructions in its DISubprogram so
that we don't need to rely on the -mllvm flag -dwarf-use-key-instructions to
determine whether or not to interpret Key Instructions metadata to decide
is_stmt placement at DWARF emission time. This makes bitcode support simple and
enables well defined mixing of non-key-instructions and key-instructions
functions in an LTO context.

This patch adds the bit (using DISubprogram::SubclassData1).

PR 144104 and 144103 use it during DWARF emission.
PR 44102 adds bitcode
support.

See pull request for overview of alternative attempts.

[KeyInstr][DwarfDebug] Add is_stmt emission support (#133495)

2025-05-13T16:26:21+00:00

Interpret Key Instructions metadata to determine is_stmt placement.

The lowest rank (highest precedent) instructions in each {InlinedAt, atomGroup}
set are candidates for is_stmt. Only the last instruction in each set in a given
block gets is_stmt. Calls always get is_stmt.

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr][LoopUnswitch] Remap cloned instructions' atoms (#133491)

2025-05-09T14:24:47+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr][JumpThreading] Remap atoms after threading (#133487)

2025-05-09T12:48:23+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr][LoopUnroll] Remap atoms while unrolling (#133489)

2025-05-09T12:47:16+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr] Remap cloned PHIs in BreakCriticalEdges (#133493)

2025-05-08T12:46:53+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr] Add MIR parser support (#133494)

2025-05-08T09:40:21+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668

[KeyInstr][LoopRotate] Remap atoms of duplicated instructions (#133490)

2025-05-07T16:10:30+00:00

RFC: https://discourse.llvm.org/t/rfc-improving-is-stmt-placement-for-better-interactive-debugging/82668