ladybird/Tests/LibJS/Bytecode/expected/named-function-expression.txt

JS bytecode executable ""
[   0]    0: GetLexicalEnvironment dst:reg4
[   8]       CreateLexicalEnvironment dst:reg5, parent:reg4, capacity:0
[  18]       CreateVariable identifier:Oops, is_immutable:true, is_global:false, is_strict:false
[  28]       NewFunction dst:reg6
[  40]       InitializeLexicalBinding identifier:Oops, src:reg6
[  58]       SetLexicalEnvironment environment:reg4
[  60]       SetGlobal identifier:Oops, src:reg6
[  70]       GetGlobal dst:reg5, identifier:Oops
[  80]       GetById dst:reg7, base:reg5, property:x, base_identifier:Oops
[  98]       End value:reg7
LibJS: Mark named function expression identifiers at individual level Previously, when parsing a named function expression like `Oops = function Oops() { Oops }`, the parser set a group-level flag `might_be_variable_in_lexical_scope_in_named_function_assignment` that propagated to the parent scope. This incorrectly prevented ALL `Oops` identifiers from being marked as global, including those outside the function expression. Fix this by marking identifiers individually using `set_is_inside_scope_with_eval()` only for identifiers inside the function scope. This allows identifiers outside the function expression to correctly use GetGlobal/SetGlobal while identifiers inside still use GetBinding (since they may refer to the function's name binding). 2026-01-26 17:37:21 -03:00			`JS bytecode executable ""`
LibJS: Replace implicit environment stack with explicit registers Replace the saved_lexical_environments stack in ExecutionContextRareData with explicit register-based environment tracking. Environments are now stored in registers and restored via SetLexicalEnvironment, making the environment flow visible in bytecode. Key changes: - Add GetLexicalEnvironment and SetLexicalEnvironment opcodes - CreateLexicalEnvironment takes explicit parent and dst operands - EnterObjectEnvironment stores new environment in a dst register - NewClass takes an explicit class_environment operand - Remove LeaveLexicalEnvironment opcode (instead: SetLexicalEnvironment) - Remove saved_lexical_environments from ExecutionContextRareData - Use a reserved register for the saved lexical environment to avoid dominance issues with lazily-emitted GetLexicalEnvironment 2026-02-08 23:34:42 -03:00			`[ 0] 0: GetLexicalEnvironment dst:reg4`
			`[ 8] CreateLexicalEnvironment dst:reg5, parent:reg4, capacity:0`
			`[ 18] CreateVariable identifier:Oops, is_immutable:true, is_global:false, is_strict:false`
			`[ 28] NewFunction dst:reg6`
			`[ 40] InitializeLexicalBinding identifier:Oops, src:reg6`
			`[ 58] SetLexicalEnvironment environment:reg4`
			`[ 60] SetGlobal identifier:Oops, src:reg6`
			`[ 70] GetGlobal dst:reg5, identifier:Oops`
			`[ 80] GetById dst:reg7, base:reg5, property:x, base_identifier:Oops`
Tests: Rebaseline bytecode tests after handler/finalizer collapse The exception handler dump format changed from showing both handler and finalizer offsets to showing only a single handler offset. 2026-02-09 08:16:05 -03:00			`[ 98] End value:reg7`