| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
can get bogus values.
llvm-svn: 89618
|
| |
|
|
| |
llvm-svn: 89576
|
| |
|
|
|
|
| |
operands, this will allow us to fold imm into comparison.
llvm-svn: 89574
|
| |
|
|
| |
llvm-svn: 89573
|
| |
|
|
| |
llvm-svn: 89572
|
| |
|
|
| |
llvm-svn: 89571
|
| |
|
|
|
|
| |
isn't necessary.
llvm-svn: 89568
|
| |
|
|
|
|
| |
backtraces.
llvm-svn: 89562
|
| |
|
|
|
|
| |
violations in ARMInstrNEON.td.
llvm-svn: 89542
|
| |
|
|
| |
llvm-svn: 89536
|
| |
|
|
|
|
| |
comma-separated string or already parsed command line parameters as input, and some code re-factoring to use these new methods.
llvm-svn: 89516
|
| |
|
|
| |
llvm-svn: 89509
|
| |
|
|
| |
llvm-svn: 89507
|
| |
|
|
|
|
| |
and support for blockaddresses in x86-32 PIC mode.
llvm-svn: 89506
|
| |
|
|
|
|
|
| |
Thanks to Daniel Dunbar for fixing clang intrinsics:
http://llvm.org/viewvc/llvm-project?view=rev&revision=89499
llvm-svn: 89500
|
| |
|
|
|
|
| |
(PPC specific).
llvm-svn: 89496
|
| |
|
|
|
|
| |
broke the Clang testsuite.
llvm-svn: 89495
|
| |
|
|
|
|
|
| |
Also fixed the corresponding testcase, and the PALIGNR
intrinsic (tested for correctness with llvm-gcc).
llvm-svn: 89491
|
| |
|
|
| |
llvm-svn: 89478
|
| |
|
|
|
|
|
|
|
|
| |
constant pool ranges, as CPEIsInRange() makes conservative assumptions about
the potential alignment changes from branch adjustments. The verification,
on the other hand, runs after those branch adjustments are made, so the
effects on alignment are known and already taken into account. The sanity
check in verify should check the range directly instead.
llvm-svn: 89473
|
| |
|
|
| |
llvm-svn: 89443
|
| |
|
|
| |
llvm-svn: 89440
|
| |
|
|
|
|
| |
immediate forms of cmov instructions at all.
llvm-svn: 89423
|
| |
|
|
| |
llvm-svn: 89414
|
| |
|
|
|
|
|
|
|
|
|
| |
assembly can confuse things utterly, as it's assumed that instructions in
inline assembly are 4 bytes wide. For Thumb mode, that's often not true,
so the calculations for when alignment padding will be present get thrown off,
ultimately leading to out of range constant pool entry references. Making
more conservative assumptions that padding may be necessary when inline asm
is present avoids this situation.
llvm-svn: 89403
|
| |
|
|
|
|
| |
change.
llvm-svn: 89396
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
$ svn merge -c -89279 https://llvm.org/svn/llvm-project/llvm/trunk
--- Reverse-merging r89279 into '.':
U lib/CodeGen/AsmPrinter/DwarfException.cpp
U lib/Target/TargetLoweringObjectFile.cpp
$ svn merge -c -89270 https://llvm.org/svn/llvm-project/llvm/trunk
--- Reverse-merging r89270 into '.':
G lib/CodeGen/AsmPrinter/DwarfException.cpp
G lib/Target/TargetLoweringObjectFile.cpp
llvm-svn: 89379
|
| |
|
|
|
|
|
|
| |
fully specified at this level. Subclasses of NLdStLN can specify selective
bit(s) for Inst{7-4}, as is done for VLD[234]LN* and VST[234]LN* inside
ARMInstrNEON.td.
llvm-svn: 89377
|
| |
|
|
| |
llvm-svn: 89369
|
| |
|
|
| |
llvm-svn: 89360
|
| |
|
|
| |
llvm-svn: 89337
|
| |
|
|
| |
llvm-svn: 89328
|
| |
|
|
| |
llvm-svn: 89326
|
| |
|
|
| |
llvm-svn: 89325
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Support mips1 like load/store of doubles:
Instead of:
sdc $f0, X($3)
Generate:
swc $f0, X($3)
swc $f1, X+4($3)
llvm-svn: 89322
|
| |
|
|
| |
llvm-svn: 89316
|
| |
|
|
|
|
| |
exception table than DataRel.
llvm-svn: 89279
|
| |
|
|
| |
llvm-svn: 89273
|
| |
|
|
|
|
| |
Place the EH table in the __TEXT section on MachO. It saves space.
llvm-svn: 89270
|
| |
|
|
|
|
| |
returns a correct feature string for given triple.
llvm-svn: 89236
|
| |
|
|
| |
llvm-svn: 89218
|
| |
|
|
| |
llvm-svn: 89214
|
| |
|
|
|
|
|
|
|
| |
contents of the block to be duplicated. Use this for ARM Cortex A8/9 to
be more aggressive tail duplicating indirect branches, since it makes it
much more likely that they will be predicted in the branch target buffer.
Testcase coming soon.
llvm-svn: 89187
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is probably not confined to *just* these two things.
Anyway, the llvm-gcc front-end may look up the structure layout information for
an abstract type. That information will be stored into a table with the FE's
TD. Instruction combine can come along and also ask for information on that
abstract type, but for a separate TD (the one associated with the pass manager).
After the type is refined, the old structure layout information in the pass
manager's TD file is out of date. If a new type is allocated in the same space
as the old-unrefined type, then the structure type information in the pass
manager's TD file will be wrong, but won't know it.
Fix this by making the TD's structure type information an abstract type user.
llvm-svn: 89176
|
| |
|
|
| |
llvm-svn: 89143
|
| |
|
|
|
|
| |
alignment imm (in the same way). Fix asmprinting for non-darwin platforms.
llvm-svn: 89137
|
| |
|
|
|
|
| |
distinguish between them and the more generic instructions (add, mov, and ldr).
llvm-svn: 89108
|
| |
|
|
| |
llvm-svn: 89081
|
| |
|
|
| |
llvm-svn: 89076
|
| |
|
|
|
|
|
| |
is analyzable so it can be updated. If it's not, be safe and don't move the
block.
llvm-svn: 89022
|