[PATCH] [extra] pptrace - preprocessor tracing and testing tool

[John Thompson]

  Sean,

  Thanks for the excellent review, and the reference to yaml-bench.  It caught a few things so far, and I'll have to use it when I write the other tests too.  It didn't like the backslashes in Windows file paths, or the colons in SourceLocations, so I put in some character replacing and quoting.

  I revised the for loops as pointed out.

  Also, I wanted to ask about the special cases, such as where I use values like (null) to represent when a pointer is null, or (invalid) when a SourceLocation has the invalid flag set.  In the former case, passing a null pointer is expected in some situations.  The YAML parser doesn't seem to mind (null), but is this reasonable semantically?

  Also, again semantically, you probably already noticed I'm not trying to flatten the full data structures for possible later resurrection, just providing what I think is sufficient high-level information to know what the preprocessor is up to.

  Kim,

  Thanks also for your help. I'll install ninja cmake and give it a shot.

  -John

Hi silvas, kimgr,

http://llvm-reviews.chandlerc.com/D2020

CHANGE SINCE LAST DIFF
  http://llvm-reviews.chandlerc.com/D2020?vs=5196&id=5210#toc

Files:
  test/pp-trace/pp-trace-macro.cpp
  pp-trace/PPTrace.cpp
  pp-trace/PPCallbacksTracker.h
  pp-trace/PPCallbacksTracker.cpp
  pp-trace/CMakeLists.txt
  pp-trace/Makefile
  CMakeLists.txt
  Makefile
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D2020.4.patch
Type: text/x-patch
Size: 48506 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20131028/36cd1098/attachment.bin>