Skip to content

Commit

Permalink
[Sema] Fix volatile check when testing if a return object can be impl…
Browse files Browse the repository at this point in the history
…icitly moved

In C++11 standard, to become implicitly movable, the expression in return
statement should be a non-volatile automatic object. CWG1579 changed the rule
to require that the expression only needs to be an automatic object. C++14
standard and C++17 standard kept this rule unchanged. C++20 standard changed
the rule back to require the expression be a non-volatile automatic object.
This should be a typo in standards, and VD should be non-volatile.

Differential Revision: https://reviews.llvm.org/D88295
  • Loading branch information
nullptr-cpp authored and Arthur O'Dwyer committed Nov 10, 2020
1 parent 6cb1c0c commit 703038b
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 3 deletions.
7 changes: 4 additions & 3 deletions clang/lib/Sema/SemaStmt.cpp
Expand Up @@ -3074,12 +3074,13 @@ bool Sema::isCopyElisionCandidate(QualType ReturnType, const VarDecl *VD,
// variable will no longer be used.
if (VD->hasAttr<BlocksAttr>()) return false;

// ...non-volatile...
if (VD->getType().isVolatileQualified())
return false;

if (CESK & CES_AllowDifferentTypes)
return true;

// ...non-volatile...
if (VD->getType().isVolatileQualified()) return false;

// Variables with higher required alignment than their type's ABI
// alignment cannot use NRVO.
if (!VD->getType()->isDependentType() && VD->hasAttr<AlignedAttr>() &&
Expand Down
26 changes: 26 additions & 0 deletions clang/test/CXX/class/class.init/class.copy.elision/p1.cpp
@@ -0,0 +1,26 @@
// RUN: %clang_cc1 -std=c++20 -emit-llvm -triple x86_64-unknown-linux-gnu -o - %s | FileCheck %s
// RUN: %clang_cc1 -std=c++17 -emit-llvm -triple x86_64-unknown-linux-gnu -o - %s | FileCheck %s
// RUN: %clang_cc1 -std=c++14 -emit-llvm -triple x86_64-unknown-linux-gnu -o - %s | FileCheck %s
// RUN: %clang_cc1 -std=c++11 -emit-llvm -triple x86_64-unknown-linux-gnu -o - %s | FileCheck %s

// - volatile object in return statement don't match the rule for using move
// operation instead of copy operation. Thus should call the copy constructor
// A(const volatile A &).
//
// - volatile object in return statement also don't match the rule for copy
// elision. Thus the copy constructor A(const volatile A &) cannot be elided.
namespace test_volatile {
class A {
public:
A() {}
~A() {}
A(const volatile A &);
A(volatile A &&);
};

A test() {
volatile A a_copy;
// CHECK: call void @_ZN13test_volatile1AC1ERVKS0_
return a_copy;
}
} // namespace test_volatile

0 comments on commit 703038b

Please sign in to comment.