diff options
author | Björn Gustavsson <[email protected]> | 2015-09-25 07:06:38 +0200 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2015-09-28 10:26:40 +0200 |
commit | 464ca2f8049feec6453d2d9a327f996662978e51 (patch) | |
tree | 3b3cfa9a9edbd98ffd821512ea8c4173780c29bf /bootstrap/lib/compiler/ebin/sys_core_fold.beam | |
parent | b66193afc3fe85072da4631c52c5ccec136caa05 (diff) | |
download | otp-464ca2f8049feec6453d2d9a327f996662978e51.tar.gz otp-464ca2f8049feec6453d2d9a327f996662978e51.tar.bz2 otp-464ca2f8049feec6453d2d9a327f996662978e51.zip |
Move select_val optimization from beam_clean to beam_peep
There is an optimization in beam_clean that will remove values
having the same label as the failure label in a select_val
instruction. Conceptually, this optimization is in the wrong
module since ideally beam_clean is a mandatory pass that should
not do optimizations. Furthermore, this part of beam_clean is
called three times (from beam_dead, beam_peep, and as a compiler
pass from the 'compile' module), but it only does useful one of
the times it is called.
Therefore, move this optimization to the beam_peep pass.
The same optimization is done in beam_dead, but unfortunately it
misses some opportunities for optimization because the code sharing
optimization in beam_jump (share/1) runs after beam_dead. It would
be more satisfactory to have this optimization only in beam_dead,
but it turned out not to be trivial. If we try to run
beam_jump:share/1 before beam_dead, some optimizations will no
longer work in beam_dead because fallthroughs have been eliminated.
For the moment, the possible solutions to this problem seems to
involve more work and more complicated code than the gain from
eliminating the duplicated optimization would gain.
Diffstat (limited to 'bootstrap/lib/compiler/ebin/sys_core_fold.beam')
0 files changed, 0 insertions, 0 deletions