actually also compile output in tests for -frewrite-includesChecking that the created output matches something is nice, butthis should also check whether the output makes sense.Differential Revi
actually also compile output in tests for -frewrite-includesChecking that the created output matches something is nice, butthis should also check whether the output makes sense.Differential Revision: https://reviews.llvm.org/D63979llvm-svn: 372250
show more ...
Fix evaluation of `__has_include_next` during -frewrite-includes.`__has_include_next` requires correct DirectoryLookup for beingevaluated correctly. We were using Preprocessor::GetCurDirLookup() b
Fix evaluation of `__has_include_next` during -frewrite-includes.`__has_include_next` requires correct DirectoryLookup for beingevaluated correctly. We were using Preprocessor::GetCurDirLookup() butwe were calling it after the preprocessor finished its work. And in thiscase CurDirLookup is always nullptr which makes `__has_include_next`behave as `__has_include`.Fix by storing and using CurDirLookup when preprocessor enters a file,not when we rewrite the includes.rdar://problem/36305026Reviewers: bkramerReviewed By: bkramerSubscribers: jkorous-apple, cfe-commitsDifferential Revision: https://reviews.llvm.org/D45603llvm-svn: 330041