[llvm-bugs] [Bug 28768] New: No way to obtain the opcode of a BinaryExpr from the C API

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Jul 29 07:48:50 PDT 2016


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

            Bug ID: 28768
           Summary: No way to obtain the opcode of a BinaryExpr from the C
                    API
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: libclang
          Assignee: unassignedclangbugs at nondot.org
          Reporter: eternaleye at gmail.com
                CC: klimek at google.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

This results in anyone unable to use the C++ API (specifically, bindings) being
unable to use libclang for actually parsing C, driving them to use other tools
(such as the Haskell Language.C library).

Relevant:

Corrode didn't use libclang due to it missing this (among other things):
https://github.com/jameysharp/corrode/issues/50#issuecomment-236098060

The libclang Rust bindings would support it if available:
https://github.com/KyleMayes/clang-rs/issues/5

-- 
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/20160729/9c4a99ad/attachment.html>


More information about the llvm-bugs mailing list