diff options
| author | Douglas Gregor <dgregor@apple.com> | 2010-08-18 00:39:00 +0000 |
|---|---|---|
| committer | Douglas Gregor <dgregor@apple.com> | 2010-08-18 00:39:00 +0000 |
| commit | 2767ce2e21d8bc17869b8436220bce719b3369e4 (patch) | |
| tree | da28a287f95cc22f3f3e6a8260aed48f359c3692 /test/Sema/array-size.c | |
| parent | 5990b5455b5e309a029a6a44889ded4e9d549f24 (diff) | |
Emit an error if an array is too large. We're slightly more strict
than GCC 4.2 here when building 32-bit (where GCC will allow
allocation of an array for which we can't get a valid past-the-end
pointer), and emulate its odd behavior in 64-bit where it only allows
63 bits worth of storage in the array. The former is a correctness
issue; the latter is harmless in practice (you wouldn't be able to use
such an array anyway) and helps us pass a GCC DejaGNU test.
Fixes <rdar://problem/8212293>.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@111338 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Sema/array-size.c')
| -rw-r--r-- | test/Sema/array-size.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/test/Sema/array-size.c b/test/Sema/array-size.c new file mode 100644 index 0000000000..7580e3ecc5 --- /dev/null +++ b/test/Sema/array-size.c @@ -0,0 +1,10 @@ +// RUN: %clang_cc1 -triple i686-apple-darwin -verify %s + +void f() { + int x0[1073741824]; // expected-error{{array is too large}} + int x1[1073741824 + 1]; // expected-error{{array is too large}} + int x2[(unsigned)1073741824]; // expected-error{{array is too large}} + int x3[(unsigned)1073741824 + 1]; // expected-error{{array is too large}} + int x4[1073741824 - 1]; +} + |