Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-09-21 | Update copyright year | Henrik Nord | |
2018-07-06 | Call test_lib:recompile/1 from init_per_suite/1 | Björn Gustavsson | |
Call test_lib:recompile/1 from init_per_suite/1 instead of from all/0. That makes it easy to find the log from the compilation in the log file for the init_per_suite/1 test case. | |||
2016-12-07 | Update copyright-year | Erlang/OTP | |
2016-05-23 | beam_reorder: Don't confuse beam_validator | Björn Gustavsson | |
Make sure we don't optimize code such as: is_tuple Fail Src test_arity Fail Src Arity get_tuple_element Src Pos Dst is_map Fail Src If we would reorder the instructions like this: is_tuple Fail Src test_arity Fail Src Arity is_map Fail Src get_tuple_element Src Pos Dst beam_validator would complain that the type for Src is a map instead of a tuple. Since the code has problems to begin with, there is no need to do the optimization. | |||
2015-10-05 | beam_reorder: Eliminate compiler crash | Björn Gustavsson | |
c288ab87 added beam_reorder to move get_tuple_element instructions. Compiling code such as the following would crash the compiler: alloc(_U1, _U2, R) -> V = R#alloc.version, Res = id(V), _ = id(0), Res. The crash would occur because the following two instructions: {get_tuple_element,{x,2},1,{x,1}}. {allocate_zero,1,2}. were swapped and rewritten to: {allocate_zero,1,1}. {get_tuple_element,{x,2},1,{x,1}}. That transformation is not safe because the allocate_zero instruction would kill {x,2}, which is the register that is holding the reference to the tuple. Only do the transformation when the tuple reference is in an x register with a lower number than the destination register. |