8006529: Methods always get callee - it should be conditional Summary: This commit streamlines the bytecode function signatures, prologue, local variable use, scope creation, and invocation. It started out quite innocently when we noticed that we always emit __callee__ parameters for all functions even when they are not needed, but it turned out to be quite a deep rabbit hole. In the end, I identified exact conditions when functions need to have a callee parameter, when they need to receive parent scope, when they need to create their own scope, when they need to have variable arity signature, and when they need to have an "arguments" object, and made sure that callee parameters in signatures only show up when they are needed, that parent function's scope is only passed to a child function when it is needed, that the function only creates its own scope when it is needed. In crypto.js, the number of scopes dropped from 446 to 244, and the number of callees dropped from 315 to 145. Reviewed-by: jlaskey, lagergren

     1

Error is a function

     2

EvalError is a function

     3

RangeError is a function

     4

ReferenceError is a function

     5

SyntaxError is a function

     6

TypeError is a function

     7

URIError is a function

     8

Error.arity 1

     9

EvalError.arity 1

    10

RangeError.arity 1

    11

ReferenceError.arity 1

    12

SyntaxError.arity 1

    13

TypeError.arity 1

    14

URIError.arity 1

    15

true

    16

my error

    17

Error

    18

thrown @ 49

    19

true

    20

ReferenceError

    21

"foo" is not defined

    22

true

    23

TypeError

    24

Cannot call undefined

    25

Error

    26

EvalError

    27

RangeError

    28

ReferenceError

    29

SyntaxError

    30

TypeError

    31

URIError