summaryrefslogtreecommitdiffstats
path: root/llvm/test/Bitcode
diff options
context:
space:
mode:
authorSterling Augustine <saugustine@google.com>2017-07-06 21:02:52 +0000
committerSterling Augustine <saugustine@google.com>2017-07-06 21:02:52 +0000
commit1cda1d76b110dca737d9c3b8dafe27bab9adbb04 (patch)
tree5444b81929bfcd7cf300f9817fe209d2aab4c24c /llvm/test/Bitcode
parent9aa45f047f303b6484afce6716472b3b1f510c7e (diff)
downloadbcm5719-llvm-1cda1d76b110dca737d9c3b8dafe27bab9adbb04.tar.gz
bcm5719-llvm-1cda1d76b110dca737d9c3b8dafe27bab9adbb04.zip
Allow CompilerInvocations to generate .d files.
Summary: Most clang tools should ignore the -M family of options because one wouldn't want them to generate a new dependency (.d) file. However, some tools may want this dependency file. This patch creates a mechanism for them to do this. This implementation just plumbs a boolean down several layers of calls. Each of the modified calls has several call sites, and so a single member variable or new API entry point won't work. An alternative would be to write a function to filter the -M family of arguments out of CC1Args, and have each caller call that function by hand before calling newInvocation, Invocation::run, or buildAstFromCodeWithArgs. This is a more complicated and error-prone solution. Why burden all the callers to remember to use this function? But I could rewrite this patch to use that method if that is deemed more appropriate. Reviewers: klimek Reviewed By: klimek Subscribers: klimek, cfe-commits Differential Revision: https://reviews.llvm.org/D34304 llvm-svn: 307315
Diffstat (limited to 'llvm/test/Bitcode')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud