beam_ssa_opt: Use is_tagged_tuple more

Consider this code:

    foo(X) ->
       case X of
         {ok,A} -> A;
         error -> X
    end.

The `is_tagged_tuple` instruction would not be used
because not all instructions in the tuple matching
sequence had the same failure label:

    function t:foo(_0) {
    0:
      @ssa_bool:7 = bif:is_tuple _0
      br @ssa_bool:7, label 8, label 4

    8:
      @ssa_arity = bif:tuple_size _0
      @ssa_bool:9 = bif:'=:=' @ssa_arity, literal 2
      br @ssa_bool:9, label 6, label 3

    6:
      _4 = get_tuple_element _0, literal 0
      @ssa_bool = bif:'=:=' _4, literal ok
      br @ssa_bool, label 5, label 3

    5:
      _3 = get_tuple_element _0, literal 1
      ret _3

    4:
      @ssa_bool:11 = bif:'=:=' _0, literal error
      br @ssa_bool:11, label 10, label 3

    10:
      ret _0

    3:
      _2 = put_tuple literal case_clause, _0

      %% t.erl:5
      @ssa_ret:12 = call remote (literal erlang):(literal error)/1, _2
      ret @ssa_ret:12
    }

Enhance the ssa_opt_record optimization to use
`is_tagged_tuple` even if all failure labels are not the
same:

    function t:foo(_0) {
    0:
      @ssa_bool:7 = bif:is_tuple _0
      br @ssa_bool:7, label 8, label 4

    8:
      @ssa_bool:9 = is_tagged_tuple _0, literal 2, literal ok
      br @ssa_bool:9, label 6, label 3

    6:
      _3 = get_tuple_element _0, literal 1
      ret _3

    4:
      @ssa_bool:11 = bif:'=:=' _0, literal error
      br @ssa_bool:11, label 10, label 3

    10:
      ret _0

    3:
      _2 = put_tuple literal case_clause, _0

      %% t.erl:5
      @ssa_ret:12 = call remote (literal erlang):(literal error)/1, _2
      ret @ssa_ret:12
    }

The tuple test will be repeated, but since four instructions
are replaced by two instructions, the code will still be faster
and smaller.

0 files changed, 0 insertions, 0 deletions