| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
the field width and precision of a format specifier instead of just
'int'. This matches GCC, and fixes <rdar://problem/6079850>.
llvm-svn: 94856
|
| |
|
|
|
|
|
| |
bit (Inst{22}) and the M bit (Inst{5}) should be left unspecified. For binary
format instructions, Inst{6} and Inst{4} need to specified for proper decodings.
llvm-svn: 94855
|
| |
|
|
|
|
| |
them from values that are not actually defined in the module.
llvm-svn: 94854
|
| |
|
|
| |
llvm-svn: 94853
|
| |
|
|
| |
llvm-svn: 94852
|
| |
|
|
|
|
| |
that returns the expected type of the matching data argument. It isn't complete, but should handle several of the important cases.
llvm-svn: 94851
|
| |
|
|
|
|
|
|
|
|
| |
create a testcase where this matters. The select+load transformation only
occurs when isSafeToLoadUnconditionally is true, and in those situations,
instcombine also changes the underlying objects to be aligned. This seems
like a good idea regardless, and I've verified that it doesn't pessimize
the subsequent realignment.
llvm-svn: 94850
|
| |
|
|
| |
llvm-svn: 94849
|
| |
|
|
| |
llvm-svn: 94848
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
<stdin>:94:1: note: possible intended match here
movsd 4096(%rsi), %xmm0
^
After:
<stdin>:94:2: note: possible intended match here
movsd 4096(%rsi), %xmm0
^
llvm-svn: 94847
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
test/CodeGen/X86/lsr-reuse.ll:52:34: error: expected string not found in input
; CHECK: movsd -2048(%rsi), %xmm0
^
After:
test/CodeGen/X86/lsr-reuse.ll:52:10: error: expected string not found in input
; CHECK: movsd -2048(%rsi), %xmm0
^
llvm-svn: 94846
|
| |
|
|
| |
llvm-svn: 94845
|
| |
|
|
|
|
| |
the library.
llvm-svn: 94844
|
| |
|
|
| |
llvm-svn: 94843
|
| |
|
|
|
|
| |
been erased (making it not have any more function-local operands)
llvm-svn: 94842
|
| |
|
|
| |
llvm-svn: 94841
|
| |
|
|
|
|
|
| |
that loads its contents lazily from bitcode. I think these are the
only remaining mis-named functions.
llvm-svn: 94840
|
| |
|
|
|
|
|
|
|
| |
suite with clang++ enabled.
The right fix here is PR6175, although we would still have to find a different
work around for the gdb test suite.
llvm-svn: 94838
|
| |
|
|
|
|
|
|
|
| |
checking. It passes all existing tests, and the diagnostics have been
refined to provide better range information (we now highlight
individual format specifiers) and more precise wording in the
diagnostics.
llvm-svn: 94837
|
| |
|
|
| |
llvm-svn: 94835
|
| |
|
|
|
|
|
|
|
|
| |
- Add ConversionSpecifier::consumesDataArgument() as a helper method
to determine if a conversion specifier requires a matching argument.
- Add support for glibc-specific '%m' conversion
- Add an extra callback to HandleNull() for locations within the
format specifier that have a null character
llvm-svn: 94834
|
| |
|
|
| |
llvm-svn: 94833
|
| |
|
|
|
|
| |
to bitfields. Add it here.
llvm-svn: 94832
|
| |
|
|
|
|
|
| |
previously, we were allowing this to bind to a temporary. Now, we
don't; add test-cases and improve diagnostics.
llvm-svn: 94831
|
| |
|
|
|
|
| |
of '='.
llvm-svn: 94830
|
| |
|
|
|
|
|
| |
indices are safe if the result is known to be within the bounds of the
underlying object.
llvm-svn: 94829
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requires a temporary. Previously, we were building an initialization
sequence that bound to the bit-field as if it were a real lvalue. Note
that we previously (and still) diagnose binding of non-const
references to bit-fields, as we should.
There's no real way to test that this code is correct, since reference
binding does not *currently* have any representation in the AST. This
fix should make it easier for that to happen, so I've verified this
fix with...
Added InitializationSequence::dump(), to print an initialization
sequence for debugging purposes.
llvm-svn: 94826
|
| |
|
|
| |
llvm-svn: 94825
|
| |
|
|
| |
llvm-svn: 94824
|
| |
|
|
| |
llvm-svn: 94823
|
| |
|
|
| |
llvm-svn: 94822
|
| |
|
|
| |
llvm-svn: 94821
|
| |
|
|
|
|
|
|
| |
check whether the basic block has a terminator or not.
This API is used by clang and the test case is test/CodeGen/debug-info-crash.c in clang module.
llvm-svn: 94820
|
| |
|
|
| |
llvm-svn: 94819
|
| |
|
|
|
|
| |
global variable.
llvm-svn: 94817
|
| |
|
|
| |
llvm-svn: 94816
|
| |
|
|
|
|
|
|
| |
that ADL is suppressed), we need to build an
UnresolvedLookupExpr. Fixes PR6063, which was hitting Boost headers
pretty hard.
llvm-svn: 94814
|
| |
|
|
| |
llvm-svn: 94813
|
| |
|
|
| |
llvm-svn: 94812
|
| |
|
|
| |
llvm-svn: 94811
|
| |
|
|
| |
llvm-svn: 94810
|
| |
|
|
| |
llvm-svn: 94809
|
| |
|
|
| |
llvm-svn: 94808
|
| |
|
|
| |
llvm-svn: 94807
|
| |
|
|
|
|
|
| |
This includes the fix in r94797 to reflect the new dependency of Sema on
Analysis.
llvm-svn: 94806
|
| |
|
|
| |
llvm-svn: 94805
|
| |
|
|
| |
llvm-svn: 94804
|
| |
|
|
| |
llvm-svn: 94803
|
| |
|
|
|
|
|
|
|
|
|
| |
KnownOne
(via APInt &RHSKnownZero = KnownZero, etc) seems dangerous and confusing to me: it
is easy not to notice this, and then wonder why KnownZero/RHSKnownZero changed
underneath you when you modified RHSKnownZero/KnownZero etc. So get rid of this.
No intended functionality change (tested with "make check" + llvm-gcc bootstrap).
llvm-svn: 94802
|
| |
|
|
|
|
| |
(fix for PR6165) are needed here too.
llvm-svn: 94801
|