diff options
| author | Heejin Ahn <aheejin@gmail.com> | 2019-01-08 01:25:12 +0000 |
|---|---|---|
| committer | Heejin Ahn <aheejin@gmail.com> | 2019-01-08 01:25:12 +0000 |
| commit | e95056d69c636ee3d8a6297e838526adf3b92eea (patch) | |
| tree | 5f6c4058383c0d50700c3b87188788e6a281022e /llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp | |
| parent | adc40baa29a1c16cde63c4bf857afea0eb7b476e (diff) | |
| download | llvm-e95056d69c636ee3d8a6297e838526adf3b92eea.zip llvm-e95056d69c636ee3d8a6297e838526adf3b92eea.tar.gz llvm-e95056d69c636ee3d8a6297e838526adf3b92eea.tar.bz2 | |
[WebAssembly] Move CFG-changing passes before RegStackify
Summary:
FixIrreducibleControlFlow and LateEHPrepare both possibly modify CFG and
create new registers. There seems to be no reason these passes go after
register-related optimization passes (PrepareForLiveIntervals,
OptimizeLiveIntervals, StoreResults, RegStackify, and RegColoring), and
this also possibly create new optimization opportunities. I think we
should put all current and future optimization passes before RegStackify
(and related passes) unless there's a reason not to.
Reviewers: kripken
Subscribers: dschuff, sbc100, sunfish, jgravelle-google, llvm-commits
Differential Revision: https://reviews.llvm.org/D56356
llvm-svn: 350596
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp')
0 files changed, 0 insertions, 0 deletions