[llvm-bugs] [Bug 30238] New: Is there a consumable format for the compiler diagnostics?

[via llvm-bugs]

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

            Bug ID: 30238
           Summary: Is there a consumable format for the compiler
                    diagnostics?
           Product: clang
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Static Analyzer
          Assignee: kremenek at apple.com
          Reporter: TrevorJamesHickey at gmail.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

There are a lot of options for formatting the output of clang's diagnostics:  
-fshow-column
-fshow-source-location
-fno-caret-diagnostics
-fno-color-diagnostics
-fdiagnostics-format=clang
-fdiagnostics-show-option
-fdiagnostics-show-category=name
-fno-diagnostics-fixit-info
-fno-diagnostics-print-source-range-info
-fdiagnostics-parseable-fixits
-fno-elide-type
-fno-diagnostics-show-template-tree

Yet none of these produce diagnostics in a structured format.   
How can one easily consume these diagnostics via another program?

I'm dealing with a huge codebase, and it would be helpful to parse all of the
diagnostics and order them by warning type, file, etc.  I was hoping I could
dump this information in XML instead of wrangling with regexes.  Are there any
plans to make that possible?  What is the best way to parse all of this
information reliably?

related SO question:  
http://stackoverflow.com/questions/36657869/how-do-i-dump-gcc-warnings-into-a-structured-format

-- 
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/20160901/90f0d9a7/attachment.html>