<html>
    <head>
      <base href="https://llvm.org/bugs/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Is there a consumable format for the compiler diagnostics?"
   href="https://llvm.org/bugs/show_bug.cgi?id=30238">30238</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Is there a consumable format for the compiler diagnostics?
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>clang
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Static Analyzer
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>kremenek@apple.com
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>TrevorJamesHickey@gmail.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>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:  
<a href="http://stackoverflow.com/questions/36657869/how-do-i-dump-gcc-warnings-into-a-structured-format">http://stackoverflow.com/questions/36657869/how-do-i-dump-gcc-warnings-into-a-structured-format</a></pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>