diff options
| author | Orlando Cazalet-Hyams <orlando.hyams@sony.com> | 2025-06-30 08:06:22 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-30 08:06:22 +0100 |
| commit | 7354123c34e658e990559a36b1ac7eb0b671e317 (patch) | |
| tree | 6ab6aac07fac2956e167b84a3d962ef5cd3ac144 /flang/lib/Frontend/CompilerInvocation.cpp | |
| parent | ed391f174b90b561b1885a9a1e9284d77bc930de (diff) | |
| download | llvm-7354123c34e658e990559a36b1ac7eb0b671e317.zip llvm-7354123c34e658e990559a36b1ac7eb0b671e317.tar.gz llvm-7354123c34e658e990559a36b1ac7eb0b671e317.tar.bz2 | |
[KeyInstr] Use DISubprogram's is-key-instructions-on flag at DWARF emission (#144104)
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.
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions