[LLVMbugs] [Bug 22781] New: Use tablegen to generate code for the debug info hierarchy

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Mar 3 17:20:07 PST 2015


http://llvm.org/bugs/show_bug.cgi?id=22781

            Bug ID: 22781
           Summary: Use tablegen to generate code for the debug info
                    hierarchy
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Core LLVM classes
          Assignee: unassignedbugs at nondot.org
          Reporter: dexonsmith at apple.com
                CC: aprantl at apple.com, dblaikie at gmail.com,
                    echristo at gmail.com, friss at apple.com,
                    llvmbugs at cs.uiuc.edu
    Classification: Unclassified

There's a much repeated code in the debug info hierarchy (from bug 22464). 
While it's fairly safe -- what wouldn't be caught a compile time is simple to
test -- it relies on somewhat opaque macros, and isn't as clean as a '.td' file
could be.

The prime candidates (in order of importance/ease/usefulness):

1. `MDNodeKeyImpl<>` specializations, in LLVMContextImpl.h.
2. The GET macros in {DebugInfo,}Metadata.h.
3. The `getImpl()` functions in {DebugInfo,}Metadata.{h,cpp}.
4. The `LLParser` routines?
5. The `AsmWriter` routines?

I'm not sure about generating the assembly handlers, and I'm fairly sure
tablegen'ing the bitcode handling is a bad idea (due to clarity about record
layout), but happy to be proven wrong!

-- 
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/20150304/4b380ec7/attachment.html>


More information about the llvm-bugs mailing list