Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-05-20 | beam_type: Remove redundant clause | Björn Gustavsson | |
The clause does not server any useful purpose, since it does the same as the default clause at the end. | |||
2010-04-19 | beam_type: Improve coalescing of fmove/2 and move/2 instructions | Björn Gustavsson | |
The following instruction sequence: fmove {fr,Fr} {x,TempXreg} move {x,TempXreg} {y,Dest} is rewritten to: fmove {fr,Fr} {y,Dest} (Provided that {x,TempXreg} is killed by the instructions following the sequence.) Generalize the optimization to also handle: fmove {fr,Fr} {x,TempXreg} move {x,TempXreg} {_,Dest} That is, the destination register can be either an X or Y register. | |||
2010-03-25 | Merge branch 'bg/compiler-remove-r11-support' into dev | Erlang/OTP | |
* bg/compiler-remove-r11-support: compiler: Don't support the no_binaries option erts: Don't support the put_string/3 instruction compiler: Don't support the no_constant_pool option compiler: Don't support the r11 option test_server: Don't support communication with R11 nodes binary_SUITE: Don't test bit-level binary roundtrips with R11 nodes erts: Test compatibility of funs with R12 instead of R11 OTP-8531 bg/compiler-remove-r11-support | |||
2010-03-22 | compiler: Don't support the no_constant_pool option | Björn Gustavsson | |
The no_constant_pool option was implied by the r11 option. It turns off the usage of the constant (literal) pool, so that BEAM instructions that use constants can be loaded in an R11 system. Since the r11 option has been removed, there is no need to retain the no_constant_pool option. | |||
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |