| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
not match
order of constructor arguments (all block API specific). This was exposed only in
a large block literal expression in a large file where PtrSet container size
execceded its limit and required reallocation. Fixes radar 7638294
llvm-svn: 95936
|
| |
|
|
|
|
|
|
|
|
| |
testb %al, %al ## <MCInst #2412 TEST8rr
## <MCOperand Reg:2>
## <MCOperand Reg:2>>
jne LBB1_7 ## <MCInst #938 JNE_1
## <MCOperand Expr:(LBB1_7)>>
llvm-svn: 95935
|
| |
|
|
|
|
|
|
| |
variable type, we can (and should) still check for completeness of the
variable's type. Do so, to work around an assertion that shows up in
Boost's shared_ptr.
llvm-svn: 95934
|
| |
|
|
|
|
| |
using 'new[]' instead of the allocator associated with ASTContext.
llvm-svn: 95933
|
| |
|
|
|
|
| |
MSVC build.
llvm-svn: 95932
|
| |
|
|
|
|
| |
assosciated with ASTContext.
llvm-svn: 95931
|
| |
|
|
|
|
| |
associated with ASTContext. This fixes yet another leak (<rdar://problem/7639260>).
llvm-svn: 95930
|
| |
|
|
|
|
|
| |
implemented, llvm-mc --show-inst now uses it to print the
instruction opcode as well as the number.
llvm-svn: 95929
|
| |
|
|
| |
llvm-svn: 95928
|
| |
|
|
|
|
|
| |
8 or 32-bit immediates, which allows the new encoder to handle
them.
llvm-svn: 95927
|
| |
|
|
| |
llvm-svn: 95926
|
| |
|
|
| |
llvm-svn: 95925
|
| |
|
|
|
|
|
| |
the tables to be const. Teach MCCodeEmitter to handle
the target-indep kinds so that we don't crash on them.
llvm-svn: 95924
|
| |
|
|
| |
llvm-svn: 95922
|
| |
|
|
| |
llvm-svn: 95921
|
| |
|
|
| |
llvm-svn: 95920
|
| |
|
|
| |
llvm-svn: 95918
|
| |
|
|
|
|
|
|
| |
tiny interval.
Also avoid division by zero.
llvm-svn: 95917
|
| |
|
|
| |
llvm-svn: 95916
|
| |
|
|
| |
llvm-svn: 95915
|
| |
|
|
|
|
| |
this).
llvm-svn: 95911
|
| |
|
|
| |
llvm-svn: 95908
|
| |
|
|
| |
llvm-svn: 95906
|
| |
|
|
| |
llvm-svn: 95904
|
| |
|
|
| |
llvm-svn: 95903
|
| |
|
|
|
|
|
| |
that generates the 1-byte and 4-byte immediate versions
from one definition.
llvm-svn: 95902
|
| |
|
|
|
|
|
| |
use a multipattern that generates both the 1-byte and 4-byte
versions from the same defm
llvm-svn: 95901
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
incompatibility and show where the structural differences are. For
example:
struct1.c:36:8: warning: type 'struct S7' has incompatible definitions
in different translation units
struct S7 { int i : 8; unsigned j : 8; } x7;
^
struct1.c:36:33: note: bit-field 'j' with type 'unsigned int' and length 8 here
struct S7 { int i : 8; unsigned j : 8; } x7;
^
struct2.c:33:33: note: bit-field 'j' with type 'unsigned int' and length 16 here
struct S7 { int i : 8; unsigned j : 16; } x7;
^
There are a few changes to make this work:
- ASTImporter now has only a single Diagnostic object, not multiple
diagnostic objects. Otherwise, having a warning/error printed via
one Diagnostic and its note printed on the other Diagnostic could
cause the note to be suppressed.
- Implemented import functionality for IntegerLiteral (along with
general support for statements and expressions)
llvm-svn: 95900
|
| |
|
|
|
|
|
|
| |
work anyway (Interpreter::getPointerToFunction doesn't return a
callable pointer), and improve the error message when an
ExecutionEngine can't be created.
llvm-svn: 95896
|
| |
|
|
| |
llvm-svn: 95895
|
| |
|
|
| |
llvm-svn: 95894
|
| |
|
|
| |
llvm-svn: 95893
|
| |
|
|
|
|
|
|
| |
VFP).
Sorry!
llvm-svn: 95892
|
| |
|
|
|
|
| |
same dead instruction.
llvm-svn: 95890
|
| |
|
|
| |
llvm-svn: 95889
|
| |
|
|
| |
llvm-svn: 95888
|
| |
|
|
|
|
| |
complete function type of the member functions (using PredefinedExpr::ComputeName.
llvm-svn: 95887
|
| |
|
|
| |
llvm-svn: 95886
|
| |
|
|
|
|
| |
A8.6.297
llvm-svn: 95885
|
| |
|
|
| |
llvm-svn: 95884
|
| |
|
|
|
|
|
| |
Use SmallVector instead of std::vector for better speed when indirectbr has
few successors.
llvm-svn: 95879
|
| |
|
|
|
|
|
|
| |
symbols.
Thanks to Duncan Sands for the testcase!
llvm-svn: 95877
|
| |
|
|
| |
llvm-svn: 95876
|
| |
|
|
| |
llvm-svn: 95874
|
| |
|
|
|
|
| |
as the "Permanently UNDEFINED" instruction.
llvm-svn: 95873
|
| |
|
|
| |
llvm-svn: 95872
|
| |
|
|
| |
llvm-svn: 95871
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
their spelling location. This prevents warnings from being swallowed just
because the caret is on the first parenthesis in, say, NULL.
This is an experiment; the risk is that there might be a substantial number
of system headers which #define symbols to expressions which inherently cause
warnings. My theory is that that's rare enough that it can be worked
around case-by-case, and that producing useful warnings around NULL is worth
it. But I'm willing to accept that I might be empirically wrong.
llvm-svn: 95870
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Enhance the printf format string checking when using the format
specifier flags ' ', '0', '+' with the 'p' or 's' conversions (since
they are nonsensical and undefined). This is similar to GCC's
checking.
Also warning when a precision is used with the 'p' conversin
specifier, since it has no meaning.
llvm-svn: 95869
|
| |
|
|
|
|
| |
fixes the remaining x86-64 jit failures afaik.
llvm-svn: 95867
|