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

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

18 lines
466 B
C++
Raw Normal View History

[clang][IFS][test][NFC] Tightening up clang-ifs tests to use -cc1 more often. Unless the test is explicitly testing a driver feature if clang interface stubs I have changed the tests to use %clang_cc1. This should make some changes I plan to make to the driver job pipeline cause fewer test changes and breakages.
2019-11-14 12:58:09 +08:00
// RUN: %clang_cc1 -o - -emit-interface-stubs %s | FileCheck %s
[clang][IFS] Adds support for more decl types in clang interface stubs. Adding support for processing the following Decls: NonTypeTemplateParmDecl, CXXConversionDecl, UnresolvedUsingValueDecl, UsingDecl, UsingShadowDecl, TypeAliasTemplateDecl, TypeAliasDecl, VarTemplateDecl, VarTemplateSpecializationDecl, UsingDirectiveDecl, TemplateTemplateParmDecl, ClassTemplatePartialSpecializationDecl, IndirectFieldDecl. Also, this allows for processing NamedDecls that don't have an identifier and skips over VarDecls that are dependent on template types. Differential Revision: https://reviews.llvm.org/D69995
2019-11-09 09:21:28 +08:00
[llvm][clang][IFS] Enhancing the llvm-ifs yaml format for symbol lists. Prior to this change the clang interface stubs format resembled something ending with a symbol list like this: Symbols: a: { Type: Func } This was problematic because we didn't actually want a map format and also because we didn't like that an empty symbol list required "Symbols: {}". That is to say without the empty {} llvm-ifs would crash on an empty list. With this new format it is much more clear which field is the symbol name, and instead the [] that is used to express an empty symbol vector is optional, ie: Symbols: - { Name: a, Type: Func } or Symbols: [] or Symbols: This further diverges the format from existing llvm-elftapi. This is a good thing because although the format originally came from the same place, they are not the same in any way. Differential Revision: https://reviews.llvm.org/D76979
2020-03-28 16:08:27 +08:00
// CHECK: --- !experimental-ifs-v2
// CHECK-NEXT: IfsVersion: 2.0
[clang][IFS][test] Fixing buildbot test fails for clang-ifs. Checking for the exact triple fails on many bots. Leaving the triple check blank.
2019-11-09 10:06:23 +08:00
// CHECK-NEXT: Triple:
[clang][IFS] Adds support for more decl types in clang interface stubs. Adding support for processing the following Decls: NonTypeTemplateParmDecl, CXXConversionDecl, UnresolvedUsingValueDecl, UsingDecl, UsingShadowDecl, TypeAliasTemplateDecl, TypeAliasDecl, VarTemplateDecl, VarTemplateSpecializationDecl, UsingDirectiveDecl, TemplateTemplateParmDecl, ClassTemplatePartialSpecializationDecl, IndirectFieldDecl. Also, this allows for processing NamedDecls that don't have an identifier and skips over VarDecls that are dependent on template types. Differential Revision: https://reviews.llvm.org/D69995
2019-11-09 09:21:28 +08:00
// CHECK-NEXT: ObjectFileFormat: ELF
// CHECK-NEXT: Symbols:
// CHECK-NEXT: ...
template<typename T> struct S2 { static unsigned f(); };
template<typename T> struct S3 { using S2<T>::f; };
typedef struct {} S4;
using ::S4;
template<typename T, T t> struct C3{};
[clang][IFS][test] Fixing buildbot test fails for clang-ifs. Checking for the exact triple fails on many bots. Leaving the triple check blank.
2019-11-09 10:06:23 +08:00
template<bool b> using U1 = C3<bool, b>;