[llvm-bugs] [Bug 37953] New: [meta] [debugify] fix -check-debugify failures

[via llvm-bugs]

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

            Bug ID: 37953
           Summary: [meta] [debugify] fix -check-debugify failures
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: greg.bedwell at sony.com
                CC: anastasis.gramm2 at gmail.com, davide at freebsd.org,
                    ftee at flametop.co.uk, llvm-bugs at lists.llvm.org,
                    paul_robinson at playstation.sony.com, vsk at apple.com
        Depends on: 37741, 37942

This is a meta bug for tracking work related to fixing all known failures from
debugify ( https://reviews.llvm.org/D40512 ).

The motivation for this is in order to provide the best possible user
experience when debugging optimized code by ensuring that optimization passes
preserve debug information wherever possible.

>From Bug 37942, Comment 1:

> An error report from -check-debugify should always be considered a compiler
> bug. It would be cumbersome if we couldn't rely on this -- so much so that
> we should consider relaxing -check-debugify rather than allowing it to emit
> false positives.


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=37741
[Bug 37741] variable information lost from debug info after combine redundant
instructions
https://bugs.llvm.org/show_bug.cgi?id=37942
[Bug 37942] [debugify] fails from Combine redundant instructions and SROA
-- 
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/20180627/e217ffbd/attachment-0001.html>