maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/ClangScanDeps/subframework_header_dir_sym...

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

25 lines
1.0 KiB
Mathematica
Raw Normal View History

[clang-scan-deps] reuse the file manager across invocations of the dependency scanner on a single worker thread This behavior can be controlled using the new `-reuse-filemanager` clang-scan-deps option. By default the file manager is reused. The added test/ClangScanDeps/symlink.cpp is able to pass with the reused filemanager after the related FileEntryRef changes landed earlier. The test test/ClangScanDeps/subframework_header_dir_symlink.m still fails when the file manager is reused (I run the FileCheck with not to make it PASS). I will address this in a follow-up patch that improves the DirectoryEntry name modelling in the FileManager. llvm-svn: 370420
2019-08-30 06:56:38 +08:00
// REQUIRES: shell
// RUN: rm -rf %t.dir
// RUN: rm -rf %t.cdb
// RUN: mkdir -p %t.dir
[clang-scan-deps][NFC] Fix tests - prevent FileCheck matching test dir path Differential Revision: https://reviews.llvm.org/D67379 llvm-svn: 371578
2019-09-11 08:30:26 +08:00
// RUN: cp %s %t.dir/subframework_header_dir_symlink_input.m
// RUN: cp %s %t.dir/subframework_header_dir_symlink_input2.m
[clang-scan-deps] reuse the file manager across invocations of the dependency scanner on a single worker thread This behavior can be controlled using the new `-reuse-filemanager` clang-scan-deps option. By default the file manager is reused. The added test/ClangScanDeps/symlink.cpp is able to pass with the reused filemanager after the related FileEntryRef changes landed earlier. The test test/ClangScanDeps/subframework_header_dir_symlink.m still fails when the file manager is reused (I run the FileCheck with not to make it PASS). I will address this in a follow-up patch that improves the DirectoryEntry name modelling in the FileManager. llvm-svn: 370420
2019-08-30 06:56:38 +08:00
// RUN: mkdir %t.dir/Inputs
// RUN: cp -R %S/Inputs/frameworks %t.dir/Inputs/frameworks
// RUN: ln -s %t.dir/Inputs/frameworks %t.dir/Inputs/frameworks_symlink
// RUN: sed -e "s|DIR|%/t.dir|g" %S/Inputs/subframework_header_dir_symlink_cdb.json > %t.cdb
[clang-scan-deps][NFC] Fix tests - prevent FileCheck matching test dir path Differential Revision: https://reviews.llvm.org/D67379 llvm-svn: 371578
2019-09-11 08:30:26 +08:00
// RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=0 | \
[clang-scan-deps] reuse the file manager across invocations of the dependency scanner on a single worker thread This behavior can be controlled using the new `-reuse-filemanager` clang-scan-deps option. By default the file manager is reused. The added test/ClangScanDeps/symlink.cpp is able to pass with the reused filemanager after the related FileEntryRef changes landed earlier. The test test/ClangScanDeps/subframework_header_dir_symlink.m still fails when the file manager is reused (I run the FileCheck with not to make it PASS). I will address this in a follow-up patch that improves the DirectoryEntry name modelling in the FileManager. llvm-svn: 370420
2019-08-30 06:56:38 +08:00
// RUN: FileCheck %s
// RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=1 | \
Introduce a DirectoryEntryRef that stores both a reference and an accessed name to the directory entry This commit introduces a parallel API that returns a DirectoryEntryRef to the FileManager, similar to the parallel FileEntryRef API. All uses will have to be update in follow-up patches. The immediate use of the new API in this patch fixes the issue where a file manager was reused in clang-scan-deps, but reported an different file path whenever a framework lookup was done through a symlink. Differential Revision: https://reviews.llvm.org/D67026 llvm-svn: 370562
2019-08-31 09:26:04 +08:00
// RUN: FileCheck %s
[clang-scan-deps] reuse the file manager across invocations of the dependency scanner on a single worker thread This behavior can be controlled using the new `-reuse-filemanager` clang-scan-deps option. By default the file manager is reused. The added test/ClangScanDeps/symlink.cpp is able to pass with the reused filemanager after the related FileEntryRef changes landed earlier. The test test/ClangScanDeps/subframework_header_dir_symlink.m still fails when the file manager is reused (I run the FileCheck with not to make it PASS). I will address this in a follow-up patch that improves the DirectoryEntry name modelling in the FileManager. llvm-svn: 370420
2019-08-30 06:56:38 +08:00
#ifndef EMPTY
#include "Framework/Framework.h"
#endif
[clang-scan-deps] Add dependency targets Differential Revision: https://reviews.llvm.org/D67475 llvm-svn: 371697
2019-09-12 08:48:45 +08:00
// CHECK: subframework_header_dir_symlink_input.o
[clang-scan-deps][NFC] Fix tests - prevent FileCheck matching test dir path Differential Revision: https://reviews.llvm.org/D67379 llvm-svn: 371578
2019-09-11 08:30:26 +08:00
// CHECK-NEXT: subframework_header_dir_symlink_input.m
[clang-scan-deps] Add dependency targets Differential Revision: https://reviews.llvm.org/D67475 llvm-svn: 371697
2019-09-12 08:48:45 +08:00
// CHECK: subframework_header_dir_symlink_input2.o
[clang-scan-deps][NFC] Fix tests - prevent FileCheck matching test dir path Differential Revision: https://reviews.llvm.org/D67379 llvm-svn: 371578
2019-09-11 08:30:26 +08:00
// CHECK-NEXT: subframework_header_dir_symlink_input2.m
[clang-scan-deps] reuse the file manager across invocations of the dependency scanner on a single worker thread This behavior can be controlled using the new `-reuse-filemanager` clang-scan-deps option. By default the file manager is reused. The added test/ClangScanDeps/symlink.cpp is able to pass with the reused filemanager after the related FileEntryRef changes landed earlier. The test test/ClangScanDeps/subframework_header_dir_symlink.m still fails when the file manager is reused (I run the FileCheck with not to make it PASS). I will address this in a follow-up patch that improves the DirectoryEntry name modelling in the FileManager. llvm-svn: 370420
2019-08-30 06:56:38 +08:00
// CHECK-NEXT: Inputs{{/|\\}}frameworks_symlink{{/|\\}}Framework.framework{{/|\\}}Headers{{/|\\}}Framework.h