mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-26 18:56:06 +00:00
39d1a0973d
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
25 lines
1.5 KiB
C++
25 lines
1.5 KiB
C++
// 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'}}
|
|
}
|