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

$615c3fdf named-function-expression.js:4:6
  Registers: 8
  Blocks:    1

block0:
  [   0] GetLexicalEnvironment dst:reg4
  [   8] CreateLexicalEnvironment dst:reg5, parent:reg4, capacity:0, is_catch_environment:false
  [  20] CreateVariable `Oops`, is_immutable:true, is_global:false, is_strict:false
  [  30] NewFunction dst:reg6, shared_function_data_index:0
  [  48] InitializeLexicalBinding `Oops`, src:reg6
  [  60] SetLexicalEnvironment environment:reg4
  [  68] SetGlobal `Oops`, src:reg6
  [  78] GetGlobal dst:reg5, `Oops`
  [  88] GetById dst:reg7, base:reg5, `x` (Oops.x)
  [  a0] End value:reg7
LibJS: Emit eager environment coordinates in bytecode Track bytecode-created declarative bindings while generating code so most environment-coordinate operands can be emitted eagerly. Dynamic lookup instructions remain for scopes where eval or object environments can change resolution at runtime. This lets the static coordinate bytecode variants run without cached- vs-uncached branches or eval poison checks, and rebaselines bytecode output for the newly eager coordinate operands. 2026-05-18 08:28:03 -03:00			`$615c3fdf named-function-expression.js:4:6`
LibJS: Improve bytecode executable dump format Add a metadata header showing register count, block count, local variable names, and the constants table. Resolve jump targets to block labels (e.g. "block1") instead of raw hex addresses, and add visual separation between basic blocks. Make identifier and property key formatting more concise by using backtick quoting and showing base_identifier as a trailing parenthetical hint that joins the base and property names. Generate a stable name for each executable by hashing the source text it covers (stable across codegen changes). Named functions show as "foo$9beb91ec", anonymous ones as "$43362f3f". Also show the source filename, line, and column. 2026-03-18 19:56:54 -03:00			`Registers: 8`
			`Blocks: 1`

			`block0:`
			`[ 0] GetLexicalEnvironment dst:reg4`
LibJS: Fix var declarations in direct eval inside catch blocks The Annex B.3.4 spec change requires distinguishing catch clause environments from other lexical environments when checking for var/let conflicts in eval, which is now tracked via a flag on DeclarativeEnvironment and propagated through the CreateLexicalEnvironment bytecode instruction from the Rust codegen. 2026-05-14 10:37:40 -03:00			`[ 8] CreateLexicalEnvironment dst:reg5, parent:reg4, capacity:0, is_catch_environment:false`
			[ 20] CreateVariable `Oops`, is_immutable:true, is_global:false, is_strict:false
			`[ 30] NewFunction dst:reg6, shared_function_data_index:0`
LibJS: Emit eager environment coordinates in bytecode Track bytecode-created declarative bindings while generating code so most environment-coordinate operands can be emitted eagerly. Dynamic lookup instructions remain for scopes where eval or object environments can change resolution at runtime. This lets the static coordinate bytecode variants run without cached- vs-uncached branches or eval poison checks, and rebaselines bytecode output for the newly eager coordinate operands. 2026-05-18 08:28:03 -03:00			[ 48] InitializeLexicalBinding `Oops`, src:reg6
			`[ 60] SetLexicalEnvironment environment:reg4`
			[ 68] SetGlobal `Oops`, src:reg6
			[ 78] GetGlobal dst:reg5, `Oops`
			[ 88] GetById dst:reg7, base:reg5, `x` (Oops.x)
			`[ a0] End value:reg7`