mirror of
https://github.com/llvm/llvm-project.git
synced 2025-05-09 09:46:06 +00:00
5055dfcf4a
There is currently no support in MSVC for using i128 as an integer literal suffix. In fact, there appears to be no evidence that they have ever supported this feature in any of their compilers. This was an over generalization of their actual feature and is a nasty source of bugs. Why is it a source of bugs? Because most code in clang expects that evaluation of an integer constant expression won't give them something that 'long long' can't represent. Instead of providing a meaningful feature, i128 gives us cute ways of exploding the compiler. llvm-svn: 243243
48 lines
1.1 KiB
C
48 lines
1.1 KiB
C
// RUN: %clang_cc1 -fsyntax-only -verify -fms-extensions %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify -fms-compatibility %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify -triple i386-pc-win32 -fms-compatibility %s
|
|
|
|
__int8 x1 = 3i8;
|
|
__int16 x2 = 4i16;
|
|
__int32 x3 = 5i32;
|
|
__int64 x5 = 0x42i64;
|
|
__int64 x6 = 0x42I64;
|
|
|
|
__int64 y = 0x42i64u; // expected-error {{invalid suffix}}
|
|
__int64 w = 0x43ui64;
|
|
__int64 z = 9Li64; // expected-error {{invalid suffix}}
|
|
__int64 q = 10lli64; // expected-error {{invalid suffix}}
|
|
|
|
__complex double c1 = 1i;
|
|
__complex double c2 = 1.0i;
|
|
__complex float c3 = 1.0if;
|
|
|
|
// radar 7562363
|
|
#define ULLONG_MAX 0xffffffffffffffffui64
|
|
#define UINT 0xffffffffui32
|
|
#define USHORT 0xffffui16
|
|
#define UCHAR 0xffui8
|
|
|
|
void a() {
|
|
unsigned long long m = ULLONG_MAX;
|
|
unsigned int n = UINT;
|
|
unsigned short s = USHORT;
|
|
unsigned char c = UCHAR;
|
|
}
|
|
|
|
void pr_7968()
|
|
{
|
|
int var1 = 0x1111111e+1;
|
|
int var2 = 0X1111111e+1;
|
|
int var3 = 0xe+1;
|
|
int var4 = 0XE+1;
|
|
|
|
int var5= 0\
|
|
x1234e+1;
|
|
|
|
int var6=
|
|
/*expected-warning {{backslash and newline separated by space}} */ 0\
|
|
x1234e+1;
|
|
}
|
|
|