Michael Kuperstein 8c65e31a5a Move SPAdj logic from PEI into the targets (NFC) ... PEI tries to keep track of how much starting or ending a call sequence adjusts the stack pointer by, so that it can resolve frame-index references. Currently, it takes a very simplistic view of how SP adjustments are done - both FrameStartOpcode and FrameDestroyOpcode adjust it exactly by the amount written in its first argument. This view is in fact incorrect for some targets (e.g. due to stack re-alignment, or because it may want to adjust the stack pointer in multiple steps). However, that doesn't cause breakage, because most targets (the only in-tree exception appears to be 32-bit ARM) rely on being able to simplify the call frame pseudo-instructions earlier, so this code is never hit. Moving the computation into TargetInstrInfo allows targets to override the way the adjustment is computed if they need to have a non-zero SPAdj. Differential Revision: http://reviews.llvm.org/D6863 llvm-svn: 225437		2015-01-08 11:04:38 +00:00
..
llvm	Move SPAdj logic from PEI into the targets (NFC)	2015-01-08 11:04:38 +00:00
llvm-c	Finish removing DestroySource.	2014-12-23 19:16:45 +00:00