blob: 899cb4cda87a29efefe11c33beaefaf18180e26f [file] [log] [blame]
Richard Smith0b458fd2012-02-04 05:35:53 +00001// RUN: %clang_cc1 -fsyntax-only -verify %s -std=c++11 -triple=i686-pc-linux-gnu
2
3void ugly_news(int *ip) {
4 // These are ill-formed according to one reading of C++98, and at the least
Stephen Hinesc568f1e2014-07-21 00:47:37 -07005 // have undefined behavior.
6 // FIXME: They're ill-formed in C++11.
Richard Smith0b458fd2012-02-04 05:35:53 +00007 (void)new int[-1]; // expected-warning {{array size is negative}}
8 (void)new int[2000000000]; // expected-warning {{array is too large}}
9}
Sebastian Redlbd45d252012-02-16 12:59:47 +000010
11
12struct S {
13 S(int);
14 S();
15 ~S();
16};
17
18struct T { // expected-note 2 {{not viable}}
19 T(int); // expected-note {{not viable}}
20};
21
22void fn() {
23 (void) new int[2] {1, 2};
24 (void) new S[2] {1, 2};
Stephen Hinesc568f1e2014-07-21 00:47:37 -070025 // C++11 [expr.new]p19:
26 // If the new-expression creates an object or an array of objects of class
27 // type, access and ambiguity control are done for the allocation function,
28 // the deallocation function (12.5), and the constructor (12.1).
29 //
30 // Note that this happens even if the array bound is constant and the
31 // initializer initializes every array element.
32 (void) new T[2] {1, 2}; // expected-error {{no matching constructor}} expected-note {{in implicit initialization of array element 2}}
Sebastian Redlbd45d252012-02-16 12:59:47 +000033}