• leszeks's avatar
    [Interpreter] Remove constant pool type in tests · b28b7e13
    leszeks authored
    For historical reasons, the interpreter's bytecode expectations tests
    required a type for the constant pool. This had two disadvantages:
    
     1. Strings and numbers were not visible in mixed pools, and
     2. Mismatches of pool types (e.g. when rebaselining) would cause parser
        errors
    
    This removes the pool types, making everything 'mixed', but appending
    the values to string and number valued constants. Specifying a pool type
    in the *.golden header now prints a warning (for backwards compatibility).
    
    BUG=v8:5350
    
    Review-Url: https://codereview.chromium.org/2310103002
    Cr-Commit-Position: refs/heads/master@{#39216}
    b28b7e13
LetVariableContextSlot.golden 3.63 KB