[llvm-bugs] [Bug 37792] New: expose debugify as an LLVM option in clang?

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Jun 13 09:48:29 PDT 2018


            Bug ID: 37792
           Summary: expose debugify as an LLVM option in clang?
           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,
                    llvm-bugs at lists.llvm.org,
                    paul_robinson at playstation.sony.com, vsk at apple.com

The workflow of doing:

$ clang -c -emit-llvm -O0 -Xclang -disable-O0-optnone test.cpp | opt
-debugify-each -disable-output -O2

is really useful for just firing source level examples through debugify
checking, but isn't practical for plugging into some existing build system or
test suite in order to put as much code through test as possible.

It would be useful if we could essentially shortcut this functionality with
something like this:

$ clang -c -O2 -mllvm -debugify-each test.cpp

I'm envisioning a future where once we've cleaned up the known debugify
failures we can enable this config on our CI systems; for example running all
of Sony's available game code regularly to have a better chance of catching
regressions as new passes are added or modified.  If we could hard-fail on
debugify errors, even better.

Definitely not high priority while there are still plenty of trivial debugify
failures out there to fix, but a "would be nice" for future.

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/20180613/b8c3c5f6/attachment.html>

More information about the llvm-bugs mailing list