summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/XCore/XCoreTargetMachine.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2012-10-18 05:31:06 +0000
committerDouglas Gregor <dgregor@apple.com>2012-10-18 05:31:06 +0000
commit112b907dbb2fe5b22719449ae15e8c3ca10ba44c (patch)
treeccacc1dc847f3bf19ce2cfe4a165c2dd7295016e /llvm/lib/Target/XCore/XCoreTargetMachine.cpp
parentb52f717411f0b312ed395fed108a5310bf591ffb (diff)
downloadbcm5719-llvm-112b907dbb2fe5b22719449ae15e8c3ca10ba44c.tar.gz
bcm5719-llvm-112b907dbb2fe5b22719449ae15e8c3ca10ba44c.zip
Start factoring the on-disk records for an AST file into a control
block, which stores information about how the AST file to generated, from the AST block, which stores the actual serialized AST. The information in the control block should be enough to determine whether the AST file is up-to-date and compatible with the current translation unit, and reading it should not cause any side effects that aren't easy to undo. That way, we can back out from an attempt to read an incompatible or out-of-date AST file. Note that there is still more factoring to do. In particular, information about the source files used to generate the AST file (along with their time stamps, sizes, etc.) still resides in the source manager block. llvm-svn: 166166
Diffstat (limited to 'llvm/lib/Target/XCore/XCoreTargetMachine.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud