hanchenye-llvm-project/clang/test/Lexer/hexfloat.cpp

// RUN: %clang_cc1 -fsyntax-only -verify -pedantic %s
// RUN: %clang_cc1 -std=c++11 -fsyntax-only -verify -pedantic %s
float f = 0x1p+1; // expected-warning{{hexadecimal floating constants are a C99 feature}}
A bug I've introduced in STDIN handling surfaced a few broken tests, fix them. Lexer/hexfloat.cpp is now XFAIL'd, I'd appreciate if someone could look into it. llvm-svn: 106840 2010-06-25 20:48:07 +08:00			`// RUN: %clang_cc1 -fsyntax-only -verify -pedantic %s`
We do parse hexfloats in C++11; make it actually work. llvm-svn: 141798 2011-10-13 02:51:02 +08:00			`// RUN: %clang_cc1 -std=c++11 -fsyntax-only -verify -pedantic %s`
			`float f = 0x1p+1; // expected-warning{{hexadecimal floating constants are a C99 feature}}`
Do not parse hexadecimal floating point literals in C++0x mode because they are incompatible with user-defined literals, specifically with the following form: 0x1p+1 The preprocessing-number token extends only as far as the 'p'; the '+' is not included. Previously we could get away with this extension as p was an invalid suffix, but now with user-defined literals, 'p' might well be a valid suffix and we are forced to consider it as such. This patch also adds a warning in non-0x C++ modes telling the user that this extension is incompatible with C++0x that is enabled by default (previously and with other languages, we warn only with a compliance option such as -pedantic). llvm-svn: 93135 2010-01-11 07:37:56 +08:00