summaryrefslogtreecommitdiffstats
path: root/llvm/utils/lit/tests/unit/TestRunner.py
diff options
context:
space:
mode:
authorDavid Callahan <dcallahan@fb.com>2017-01-25 01:55:28 +0000
committerDavid Callahan <dcallahan@fb.com>2017-01-25 01:55:28 +0000
commitae7e0da4f8a746f888b398cd42a245ef9456b045 (patch)
tree582d31c937305f4a40b7b3b26cbb32c2f5c07164 /llvm/utils/lit/tests/unit/TestRunner.py
parent86f9e46365d64c56dd2adc656e4beead9aa4f4ec (diff)
downloadbcm5719-llvm-ae7e0da4f8a746f888b398cd42a245ef9456b045.tar.gz
bcm5719-llvm-ae7e0da4f8a746f888b398cd42a245ef9456b045.zip
Use filename in linemarker when compiling preprocessed source
Summary: Clang appears to always use name as specified on the command line, whereas gcc uses the name as specified in the linemarker at the first line when compiling a preprocessed source. This results mismatch between two compilers in FILE symbol table entry. This patch makes clang to resemble gcc's behavior in finding the original source file name and use it as an input file name. Even with this patch, values of FILE symbol table entry may still be different because clang uses dirname+basename for the entry whlie gcc uses basename only. I'll write a patch for that once this patch is committed. Reviewers: dblaikie, inglorion Reviewed By: inglorion Subscribers: inglorion, aprantl, bruno Differential Revision: https://reviews.llvm.org/D28796 llvm-svn: 293004
Diffstat (limited to 'llvm/utils/lit/tests/unit/TestRunner.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud