History log of /llvm-project/llvm/lib/CodeGen/PrologEpilogInserter.cpp (Results 376 – 400 of 502)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: llvmorg-2.5.0
# 5a913d61 28-Jan-2009 Duncan Sands <baldrick@free.fr>

Rename getAnalysisToUpdate to getAnalysisIfAvailable.

llvm-svn: 63198


Revision tags: llvmorg-2.4.0
# 1af23b03 07-Nov-2008 Bill Wendling <isanbard@gmail.com>

Refactor code that adjusts the offsets of stack objects.

llvm-svn: 58829


# 8b47c1e0 06-Nov-2008 Bill Wendling <isanbard@gmail.com>

Don't recalculate the stack position of the stack protector.

llvm-svn: 58815


# b3f7a398 06-Nov-2008 Bill Wendling <isanbard@gmail.com>

- Rename stackprotector_{prologue,epilogue} to stackprotector_{create,check}.
- Get rid of "HasStackProtector" in MachineFrameInfo.
- Modify intrinsics to tell which are doing what with memory.

llvm

- Rename stackprotector_{prologue,epilogue} to stackprotector_{create,check}.
- Get rid of "HasStackProtector" in MachineFrameInfo.
- Modify intrinsics to tell which are doing what with memory.

llvm-svn: 58799

show more ...


# d970ea3e 06-Nov-2008 Bill Wendling <isanbard@gmail.com>

Implement the stack protector stack accesses via intrinsics:

- stackprotector_prologue creates a stack object and stores the guard there.

- stackprotector_epilogue reads the stack guard from the st

Implement the stack protector stack accesses via intrinsics:

- stackprotector_prologue creates a stack object and stores the guard there.

- stackprotector_epilogue reads the stack guard from the stack position created
by stackprotector_prologue.

- The PrologEpilogInserter was changed to make sure that the stack guard is
first on the stack frame.

llvm-svn: 58791

show more ...


# d2bc1338 31-Oct-2008 Bill Wendling <isanbard@gmail.com>

Revert r58489. It isn't correct for all cases.

llvm-svn: 58523


# 6d70df0b 31-Oct-2008 Bill Wendling <isanbard@gmail.com>

Don't skip over all "terminator" instructions when determining where to put the
callee-saved restore code. It could skip over conditional jumps
accidentally. Instead, just skip the "return" instructi

Don't skip over all "terminator" instructions when determining where to put the
callee-saved restore code. It could skip over conditional jumps
accidentally. Instead, just skip the "return" instructions.

llvm-svn: 58489

show more ...


# 0d1e9a8e 03-Oct-2008 Dan Gohman <gohman@apple.com>

Switch the MachineOperand accessors back to the short names like
isReg, etc., from isRegister, etc.

llvm-svn: 57006


# 962c2cf1 22-Sep-2008 Evan Cheng <evan.cheng@apple.com>

Instead of setPreservesAll, just mark them preseving machine loop info and machine dominators.

llvm-svn: 56475


# 168f8f39 22-Sep-2008 Evan Cheng <evan.cheng@apple.com>

Mark several codegen passes as preserving all analysis.

llvm-svn: 56469


# a79db30d 04-Sep-2008 Dan Gohman <gohman@apple.com>

Tidy up several unbeseeming casts from pointer to intptr_t.

llvm-svn: 55779


# 26ffe2be 16-Jul-2008 Dan Gohman <gohman@apple.com>

Fix a comment to say nonnegative instead of positive.

llvm-svn: 53681


# 659aeb61 30-Jun-2008 Dale Johannesen <dalej@apple.com>

No need to align the stack if there are no stack
objects. Fixes a couple of tests on Linux.

llvm-svn: 52921


# a2de8eab 26-Jun-2008 Dale Johannesen <dalej@apple.com>

Fixes the last x86-64 test failure in compat.exp:
<16 x float> is 64-byte aligned (for some reason),
which gets us into the stack realignment code. The
computation changing FP-relative offsets to SP

Fixes the last x86-64 test failure in compat.exp:
<16 x float> is 64-byte aligned (for some reason),
which gets us into the stack realignment code. The
computation changing FP-relative offsets to SP-relative
was broken, assiging a spill temp to a location
also used for parameter passing. This
fixes it by rounding up the stack frame to a multiple
of the largest alignment (I concluded it wasn't fixable
without doing this, but I'm not very sure.)

llvm-svn: 52750

show more ...


Revision tags: llvmorg-2.3.0
# 2dd8fdc7 03-Jun-2008 Bruno Cardoso Lopes <bruno.cardoso@gmail.com>

Fixed bug in bad behavior in calculateFrameObjectOffsets,
the solution commited is different from the previous patch to
avoid int and unsigned comparison

llvm-svn: 51899


# 41334635 23-Apr-2008 Anton Korobeynikov <asl@math.spbu.ru>

Use precomputed value, if any

llvm-svn: 50164


# f49bc9f8 23-Apr-2008 Anton Korobeynikov <asl@math.spbu.ru>

Cleanup

llvm-svn: 50160


# a7cca362 20-Mar-2008 Chris Lattner <sabre@nondot.org>

detabify llvm, patch by Mike Stump!

llvm-svn: 48577


# 0e541ea7 03-Mar-2008 Bill Wendling <isanbard@gmail.com>

Miscellaneous clean-ups based on Evan's feedback:

- Cleaned up how the prologue-epilogue inserter loops over the instructions.
- Instead of restarting the processing of an instruction if we remove a

Miscellaneous clean-ups based on Evan's feedback:

- Cleaned up how the prologue-epilogue inserter loops over the instructions.
- Instead of restarting the processing of an instruction if we remove an
implicit kill, just update the end iterator and make sure that the iterator
isn't incremented.

llvm-svn: 47870

show more ...


# 4836d58f 03-Mar-2008 Bill Wendling <isanbard@gmail.com>

Multiple instructions can be inserted when eliminating frame indexes. We need
the register scavenger to process all of those new instructions instead of just
the last one inserted.

llvm-svn: 47860


# 8ae8e2d5 27-Feb-2008 Evan Cheng <evan.cheng@apple.com>

Don't track max alignment during stack object allocations since they can be deleted later. Let PEI compute it.

llvm-svn: 47668


# 6d56368c 27-Feb-2008 Evan Cheng <evan.cheng@apple.com>

Spiller now remove unused spill slots.

llvm-svn: 47657


# 963192f4 21-Feb-2008 Bill Wendling <isanbard@gmail.com>

Adjust the MaxAlignment for the special register scavenging spill slot.

llvm-svn: 47452


Revision tags: llvmorg-2.2.0
# 3a4be0fd 10-Feb-2008 Dan Gohman <gohman@apple.com>

Rename MRegisterInfo to TargetRegisterInfo.

llvm-svn: 46930


# efd142a9 02-Feb-2008 Evan Cheng <evan.cheng@apple.com>

SDIsel processes llvm.dbg.declare by recording the variable debug information descriptor and its corresponding stack frame index in MachineModuleInfo. This only works if the local variable is "homed"

SDIsel processes llvm.dbg.declare by recording the variable debug information descriptor and its corresponding stack frame index in MachineModuleInfo. This only works if the local variable is "homed" in the stack frame. It does not work for byval parameter, etc.
Added ISD::DECLARE node type to represent llvm.dbg.declare intrinsic. Now the intrinsic calls are lowered into a SDNode and lives on through out the codegen passes.
For now, since all the debugging information recording is done at isel time, when a ISD::DECLARE node is selected, it has the side effect of also recording the variable. This is a short term solution that should be fixed in time.

llvm-svn: 46659

show more ...


1...<<1112131415161718192021