| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
We want to catch both negative and positive failure conditions.
llvm-svn: 211449
|
|
|
|
|
|
|
|
| |
This Lexer test unconditionally used the i128 integer literal suffix.
This suffix is only available to targets that have 128-bit arithmetic
support.
llvm-svn: 211446
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D3963
llvm-svn: 209859
|
|
|
|
| |
llvm-svn: 142797
|
|
|
|
|
|
| |
by Martin Vejnar!
llvm-svn: 116460
|
|
|
|
|
|
| |
patch by Francois Pichet!
llvm-svn: 112602
|
|
|
|
|
|
|
| |
the pp-number in a hexadecimal floating point literal, from Francois
Pichet! Fixes PR7968.
llvm-svn: 112481
|
|
llvm-svn: 108622
|