diff options
author | Erich Keane <erich.keane@intel.com> | 2020-04-08 13:14:33 -0700 |
---|---|---|
committer | Erich Keane <erich.keane@intel.com> | 2020-04-08 13:19:55 -0700 |
commit | 30588a739584bb8ac41715d68656d22bd85198e7 (patch) | |
tree | dfd35280a3d4d1d8739d438ed419fce3fccf9dbc /clang/lib/CodeGen/CGClass.cpp | |
parent | eceae25f6d9a29303573859841481c24033f58e6 (diff) | |
download | llvm-30588a739584bb8ac41715d68656d22bd85198e7.zip llvm-30588a739584bb8ac41715d68656d22bd85198e7.tar.gz llvm-30588a739584bb8ac41715d68656d22bd85198e7.tar.bz2 |
Make target features check work with ctor and dtor-
The problem was reported in PR45468, applying target features to an
always_inline constructor/destructor runs afoul of GlobalDecl
construction assert when checking for target-feature compatibility.
The core problem is fixed by using the version of the check that takes a
FunctionDecl rather than the GlobalDecl. However, while writing the
test, I discovered that source locations weren't properly set for this
check on ctors/dtors. This patch also fixes constructors and CALLED destructors.
Unfortunately, it doesn't seem too possible to get a meaningful source
location for a 'cleanup' destructor, so those are still 'frontend' level
errors unfortunately. A fixme was added to the test to cover that
situation.
Diffstat (limited to 'clang/lib/CodeGen/CGClass.cpp')
-rw-r--r-- | clang/lib/CodeGen/CGClass.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/lib/CodeGen/CGClass.cpp b/clang/lib/CodeGen/CGClass.cpp index 73c522a..017a29e 100644 --- a/clang/lib/CodeGen/CGClass.cpp +++ b/clang/lib/CodeGen/CGClass.cpp @@ -2174,7 +2174,7 @@ void CodeGenFunction::EmitCXXConstructorCall(const CXXConstructorDecl *D, const CGFunctionInfo &Info = CGM.getTypes().arrangeCXXConstructorCall( Args, D, Type, ExtraArgs.Prefix, ExtraArgs.Suffix, PassPrototypeArgs); CGCallee Callee = CGCallee::forDirect(CalleePtr, GlobalDecl(D, Type)); - EmitCall(Info, Callee, ReturnValueSlot(), Args); + EmitCall(Info, Callee, ReturnValueSlot(), Args, nullptr, Loc); // Generate vtable assumptions if we're constructing a complete object // with a vtable. We don't do this for base subobjects for two reasons: |