maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Modules/libstdcxx-ambiguous-interna...

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

14 lines
857 B
C++
Raw Normal View History

[modules] libstdc++ defines some static inline functions in its internal headers. If those headers end up being textually included twice into the same module, we get ambiguity errors. Work around this by downgrading the ambiguity error to a warning if multiple identical internal-linkage functions appear in an overload set, and just pick one of those functions as the lookup result. llvm-svn: 250884
2015-10-21 15:13:52 +08:00
// RUN: rm -rf %t
// RUN: %clang_cc1 -x c++ -std=c++11 -fmodules -emit-module -fmodule-name=std -fmodules-cache-path=%t %S/Inputs/libstdcxx-ambiguous-internal/module.modulemap -Werror
// RUN: %clang_cc1 -x c++ -std=c++11 -fmodules -emit-module -fmodule-name=std -fmodules-cache-path=%t %S/Inputs/libstdcxx-ambiguous-internal/module.modulemap -fmodules-local-submodule-visibility -DAMBIGUOUS 2>&1| FileCheck %s
// CHECK-NOT: error
[modules] Generalize the workaround for multiple ambiguous definitions of internal linkage entities in different modules from r250884 to apply to all names, not just function names. This is really awkward: we don't want to merge internal-linkage symbols from separate modules, because they might not actually be defining the same entity. But we don't want to reject programs that use such an ambiguous symbol if those internal-linkage symbols are in fact equivalent. For now, we're resolving the ambiguity by picking one of the equivalent definitions as an extension. llvm-svn: 252063
2015-11-05 03:26:32 +08:00
// CHECK: warning: ambiguous use of internal linkage declaration 'f' defined in multiple modules
// CHECK: note: declared here in module 'std.C'
// CHECK: note: declared here in module 'std.B'
// CHECK-NOT: error
// CHECK: warning: ambiguous use of internal linkage declaration 'n' defined in multiple modules
// CHECK: note: declared here in module 'std.C'
// CHECK: note: declared here in module 'std.B'
[modules] libstdc++ defines some static inline functions in its internal headers. If those headers end up being textually included twice into the same module, we get ambiguity errors. Work around this by downgrading the ambiguity error to a warning if multiple identical internal-linkage functions appear in an overload set, and just pick one of those functions as the lookup result. llvm-svn: 250884
2015-10-21 15:13:52 +08:00
// CHECK-NOT: error