summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/support/gmodules.py
diff options
context:
space:
mode:
authorZvi Rackover <zvi.rackover@intel.com>2017-10-24 12:13:05 +0000
committerZvi Rackover <zvi.rackover@intel.com>2017-10-24 12:13:05 +0000
commit31b101a18613e1bbe6e3b5a630a2359be1be4f4b (patch)
tree6919220a9e84783a3d9d364793a2a2d6a0f376aa /lldb/packages/Python/lldbsuite/support/gmodules.py
parent1c043a9f28629929719c7262c74f837476416d43 (diff)
downloadbcm5719-llvm-31b101a18613e1bbe6e3b5a630a2359be1be4f4b.tar.gz
bcm5719-llvm-31b101a18613e1bbe6e3b5a630a2359be1be4f4b.zip
X86CallFrameOptimization: Recognize 'store 0/-1 using and/or' idioms
Summary: r264440 added or/and patterns for storing -1 or 0 with the intention of decreasing code size. However, X86CallFrameOptimization does not recognize these memory accesses so it will not replace them with push's when profitable. This patch fixes this problem by teaching X86CallFrameOptimization these store 0/-1 idioms. An alternative fix would be to prevent the 'store 0/1 idioms' patterns from firing when accessing the stack. This would save the need to teach the pass about these idioms. However, because X86CallFrameOptimization does not always fire we may result in cases where neither X86CallFrameOptimization not the patterns for 'store 0/1 idioms' fire. Fixes pr34863 Reviewers: DavidKreitzer, guyblank, aymanmus Reviewed By: aymanmus Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D38738 llvm-svn: 316431
Diffstat (limited to 'lldb/packages/Python/lldbsuite/support/gmodules.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud