[llvm-bugs] [Bug 37728] New: [meta] Make llvm passes debug info invariant
via llvm-bugs
llvm-bugs at lists.llvm.org
Thu Jun 7 00:52:58 PDT 2018
https://bugs.llvm.org/show_bug.cgi?id=37728
Bug ID: 37728
Summary: [meta] Make llvm passes debug info invariant
Product: new-bugs
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: vsk at apple.com
CC: llvm-bugs at lists.llvm.org
This is a meta bug for tracking work related to making llvm passes debug info
invariant. That means that the output of llvm passes should be the same, modulo
debug info metadata & intrinsics, regardless of whether the input IR contains
debug info. The motivation for this is that enabling debug info should not
degrade optimizations.
There are at least two different approaches for detecting debug invariance
bugs:
1. Compile a C program with/without -g, and check that the resulting text
sections are identical.
2. Compile some LLVM IR using opt, with/without -debugify-each enabled, and
check that the stripped output is identical. The -debugify-each mode
applies/removes synthetic debug info to a Module before/after each pass in
opt's pipeline.
The second approach might be a bit more flexible, seeing as it's possible to
generate LLVM IR from a C program, and to then run a custom pipeline over the
IR using opt.
In addition to finding debug invariance bugs, we should think about setting up
infrastructure to detect regressions, and about adding utilities to the
codebase which might make it easier to write debug info invariant passes.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180607/587097e8/attachment-0001.html>
More information about the llvm-bugs
mailing list