- Oct 15, 2010
-
-
Jakob Stoklund Olesen authored
splitting or spillling, and to help with rematerialization. Use LiveRangeEdit in InlineSpiller and SplitKit. This will eventually make it possible to share remat code between InlineSpiller and SplitKit. llvm-svn: 116543
-
- Oct 14, 2010
-
-
Jakob Stoklund Olesen authored
Before we would also split around a loop if any peripheral block had multiple uses. This could cause repeated splitting when splitting a different live range would insert uses into the periphery. Now -spiller=inline passes the nightly test suite again. llvm-svn: 116494
-
Evan Cheng authored
llvm-svn: 116465
-
- Oct 13, 2010
-
-
Owen Anderson authored
llvm-svn: 116441
-
- Oct 12, 2010
-
-
Owen Anderson authored
perform initialization without static constructors AND without explicit initialization by the client. For the moment, passes are required to initialize both their (potential) dependencies and any passes they preserve. I hope to be able to relax the latter requirement in the future. llvm-svn: 116334
-
- Oct 11, 2010
-
-
Jakob Stoklund Olesen authored
This helps hiding the LiveRange class which really should be private. llvm-svn: 116244
-
Jakob Stoklund Olesen authored
LocalRewriter. This is a bit of a hack that adds an implicit use operand to model the read-modify-write nature of a partial redef. Uses and defs are rewritten in separate passes, and a single operand would never be processed twice. <rdar://problem/8518892> llvm-svn: 116210
-
Chris Lattner authored
it comes back, it will be largely a rewrite, so keeping the old codebase in tree isn't helping anyone. llvm-svn: 116190
-
- Oct 10, 2010
-
-
Chris Lattner authored
truncate the stack pointer to 32-bits on a 64-bit machine. llvm-svn: 116169
-
- Oct 09, 2010
-
-
Benjamin Kramer authored
llvm-svn: 116156
-
Jakob Stoklund Olesen authored
functions: computeRemainder and rewrite. When the remainder breaks up into multiple components, remember to rewrite those uses as well. llvm-svn: 116121
-
Evan Cheng authored
llvm-svn: 116119
-
Jakob Stoklund Olesen authored
are still way too long, but it's a start. No functional change intended. llvm-svn: 116116
-
- Oct 08, 2010
-
-
Anton Korobeynikov authored
Such a check does not make any sense in presense of inlining and other compiler-dependent stuff. This should fix bunch of warnings on mingw32. llvm-svn: 116113
-
Jakob Stoklund Olesen authored
llvm-svn: 116105
-
Rafael Espindola authored
are easier to diff with those produced by llvm-mc. llvm-svn: 116095
-
Evan Cheng authored
llvm-svn: 116081
-
Evan Cheng authored
implicit. e.g. %D6<def>, %D7<def> = VLD1q16 %R2<kill>, 0, ..., %Q3<imp-def> %Q1<def> = VMULv8i16 %Q1<kill>, %Q3<kill>, ... The real definition indices are 0,1. llvm-svn: 116080
-
Devang Patel authored
llvm-svn: 116061
-
Jakob Stoklund Olesen authored
connected components. These components should be allocated different virtual registers because there is no reason for them to be allocated together. Add the ConnectedVNInfoEqClasses class to calculate the connected components, and move values to new LiveIntervals. Use it from SplitKit::rewrite by creating new virtual registers for the components. llvm-svn: 116006
-
Owen Anderson authored
llvm-svn: 115996
-
Devang Patel authored
llvm-svn: 115988
-
- Oct 07, 2010
-
-
Jakob Stoklund Olesen authored
llvm-svn: 115951
-
Jakob Stoklund Olesen authored
llvm-svn: 115950
-
Owen Anderson authored
llvm-svn: 115949
-
Jakob Stoklund Olesen authored
do one find(). llvm-svn: 115929
-
Jakob Stoklund Olesen authored
llvm-svn: 115928
-
Jakob Stoklund Olesen authored
This function is intended to be used when inserting a machine instruction that trivially restricts the legal registers, like LEA requiring a GR32_NOSP argument. llvm-svn: 115875
-
Jakob Stoklund Olesen authored
llvm-svn: 115874
-
- Oct 06, 2010
-
-
Owen Anderson authored
llvm-svn: 115835
-
Devang Patel authored
llvm-svn: 115833
-
Nick Lewycky authored
llvm-svn: 115802
-
Dan Gohman authored
llvm-svn: 115792
-
Evan Cheng authored
allow target to correctly compute latency for cases where static scheduling itineraries isn't sufficient. e.g. variable_ops instructions such as ARM::ldm. This also allows target without scheduling itineraries to compute operand latencies. e.g. X86 can return (approximated) latencies for high latency instructions such as division. - Compute operand latencies for those defined by load multiple instructions, e.g. ldm and those used by store multiple instructions, e.g. stm. llvm-svn: 115755
-
Jakob Stoklund Olesen authored
llvm-svn: 115710
-
Jakob Stoklund Olesen authored
reusable, but that is no longer relevant since a split will always replace the original. llvm-svn: 115709
-
Jakob Stoklund Olesen authored
llvm-svn: 115708
-
Jakob Stoklund Olesen authored
llvm-svn: 115696
-
Jakob Stoklund Olesen authored
never kept after splitting. Keeping the original interval made sense when the split region doesn't modify the register, and the original is spilled. We can get the same effect by detecting reloaded values when spilling around copies. llvm-svn: 115695
-
Jakob Stoklund Olesen authored
llvm-svn: 115694
-