[llvm-bugs] [Bug 41869] New: [DebugInfo] DbgEntityHistoryCalculator assumes "last" block is exit block

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=41869

            Bug ID: 41869
           Summary: [DebugInfo] DbgEntityHistoryCalculator assumes "last"
                    block is exit block
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Keywords: wrong-debug
          Severity: normal
          Priority: P
         Component: Common Code Generator Code
          Assignee: unassignedbugs at nondot.org
          Reporter: jeremy.morse.llvm at gmail.com
                CC: chackz0x12 at gmail.com, david.stenberg at ericsson.com,
                    greg.bedwell at sony.com, llvm-bugs at lists.llvm.org,
                    orlando.hyams at sony.com, paul.robinson at am.sony.com,
                    stephen.tozer at sony.com

As it stands, DbgEntityHistoryCalculator currently makes the assumption [0]
that the last (by order) basic block in a function is the exit block. This
sometimes isn't true, for various reasons (block layout, PGO, tail duplication
etc) and yet "open ended" debug locations are something that other parts of
DwarfDebug rely on, for example the validThroughout function.

This probably isn't a high priority item given other debuginfo problems; but
something that should eventually be addressed.

[0]
https://github.com/llvm/llvm-project/blob/c93f56d39e629b7bcd0f4657705264fcd7e47c0d/llvm/lib/CodeGen/AsmPrinter/DbgEntityHistoryCalculator.cpp#L355

-- 
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/20190514/751dec21/attachment.html>