Forbid the use of C++ new/delete to allocate/free objects within an

address space. I could see that this functionality would be useful,
but not in its current form (where the address space is ignored):
rather, we'd want to encode the address space into the parameter list
passed to operator new/operator delete somehow, which would require a
bunch more semantic analysis.

llvm-svn: 129593
This commit is contained in:
Douglas Gregor 2011-04-15 19:46:20 +00:00
parent a3a020ae0b
commit 39d1a0973d
3 changed files with 37 additions and 3 deletions

View File

@ -2927,7 +2927,11 @@ def ext_array_size_conversion : Extension<
"implicit conversion from array size expression of type %0 to "
"%select{integral|enumeration}1 type %2 is a C++0x extension">,
InGroup<CXX0x>;
def err_address_space_qualified_new : Error<
"'new' cannot allocate objects of type %0 in address space '%1'">;
def err_address_space_qualified_delete : Error<
"'delete' cannot delete objects of type %0 in address space '%1'">;
def err_default_init_const : Error<
"default initialization of an object of const type %0"
"%select{| requires a user-provided default constructor}1">;

View File

@ -1104,7 +1104,10 @@ bool Sema::CheckAllocatedType(QualType AllocType, SourceLocation Loc,
else if (AllocType->isVariablyModifiedType())
return Diag(Loc, diag::err_variably_modified_new_type)
<< AllocType;
else if (unsigned AddressSpace = AllocType.getAddressSpace())
return Diag(Loc, diag::err_address_space_qualified_new)
<< AllocType.getUnqualifiedType() << AddressSpace;
return false;
}
@ -1725,7 +1728,10 @@ Sema::ActOnCXXDelete(SourceLocation StartLoc, bool UseGlobal,
PDiag(diag::warn_delete_incomplete)
<< Ex.get()->getSourceRange()))
return ExprError();
else if (unsigned AddressSpace = Pointee.getAddressSpace())
return Diag(Ex.get()->getLocStart(),
diag::err_address_space_qualified_delete)
<< Pointee.getUnqualifiedType() << AddressSpace;
// C++ [expr.delete]p2:
// [Note: a pointer to a const type can be the operand of a
// delete-expression; it is not necessary to cast away the constness

View File

@ -0,0 +1,24 @@
// RUN: %clang_cc1 -fsyntax-only -verify %s
void* operator new (__SIZE_TYPE__ size, void* ptr);
void* operator new[](__SIZE_TYPE__ size, void* ptr);
typedef int __attribute__((address_space(1))) int_1;
void test_new(void *p) {
(void)new int_1; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new __attribute__((address_space(1))) int; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new int_1 [5]; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new __attribute__((address_space(1))) int [5]; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
// Placement new
(void)new (p) int_1; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new (p) __attribute__((address_space(1))) int; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new (p) int_1 [5]; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
(void)new (p) __attribute__((address_space(1))) int [5]; // expected-error{{'new' cannot allocate objects of type 'int' in address space '1'}}
}
void test_delete(int_1 *ip1) {
delete ip1; // expected-error{{'delete' cannot delete objects of type 'int' in address space '1'}}
delete [] ip1; // expected-error{{'delete' cannot delete objects of type 'int' in address space '1'}}
}