From 0bae624934ccee9434893025fc80cfd4bbd8eec8 Mon Sep 17 00:00:00 2001 From: Richard Smith Date: Thu, 25 Aug 2016 00:34:00 +0000 Subject: Lazily load the ContextDecl for a lambda's DefinitionData, to fix a deserialization cycle caused by the ContextDecl recursively importing members of the lambda's closure type. llvm-svn: 279694 --- clang/test/Modules/lambda-context.cpp | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 clang/test/Modules/lambda-context.cpp (limited to 'clang/test/Modules/lambda-context.cpp') diff --git a/clang/test/Modules/lambda-context.cpp b/clang/test/Modules/lambda-context.cpp new file mode 100644 index 00000000000..6ce482c2b76 --- /dev/null +++ b/clang/test/Modules/lambda-context.cpp @@ -0,0 +1,22 @@ +// RUN: %clang_cc1 -fmodules -std=c++11 -emit-pch -o %t %s +// RUN: %clang_cc1 -fmodules -std=c++11 -include-pch %t %s -verify +// +// This test checks for a bug in the deserialization code that was only +// reachable with modules enabled, but actually building and using modules is +// not necessary in order to trigger it, so we just use PCH here to make the +// test simpler. + +#ifndef HEADER_INCLUDED +#define HEADER_INCLUDED + +struct X { template X(T) {} }; +struct Y { Y(X x = [] {}); }; + +#else + +// This triggers us to load the specialization of X::X for Y's lambda. That +// lambda's context decl must not be loaded as a result of loading the lambda, +// as that would hit a deserialization cycle. +X x = [] {}; // expected-no-diagnostics + +#endif -- cgit v1.2.3