ladybird/Meta/CMake/libjs_generators.cmake

function(generate_bytecode_def_derived)
    set(LIBJS_INPUT_FOLDER "${CMAKE_CURRENT_SOURCE_DIR}")
    invoke_py_generator(
            "Op.cpp"
            "generate_libjs_bytecode_def_derived.py"
            "${LIBJS_INPUT_FOLDER}/Bytecode/Bytecode.def"
            "Bytecode/Op.h"
            "Bytecode/Op.cpp"
            EXTRA_HEADER "Bytecode/OpCodes.h"
            arguments -i "${LIBJS_INPUT_FOLDER}/Bytecode/Bytecode.def"
    )
endfunction()
LibJS: Generate C++ bytecode instruction classes from a definition file This commit adds a new Bytecode.def file that describes all the LibJS bytecode instructions. From this, we are able to generate the full declarations for all C++ bytecode instruction classes, as well as their serialization code. Note that some of the bytecode compiler was updated since instructions no longer have default constructor arguments. The big immediate benefit here is that we lose a couple thousand lines of hand-written C++ code. Going forward, this also allows us to do more tooling for the bytecode VM, now that we have an authoritative description of its instructions. Key things to know about: - Instructions can inherit from one another. At the moment, everything simply inherits from the base "Instruction". - @terminator means the instruction terminates a basic block. - @nothrow means the instruction cannot throw. This affects how the interpreter interacts with it. - Variable-length instructions are automatically supported. Just put an array of something as the last field of the instruction. - The m_length field is magical. If present, it will be populated with the full length of the instruction. This is used for variable-length instructions. 2025-11-20 18:14:50 -03:00			`function(generate_bytecode_def_derived)`
			`set(LIBJS_INPUT_FOLDER "${CMAKE_CURRENT_SOURCE_DIR}")`
			`invoke_py_generator(`
			`"Op.cpp"`
Meta: Move python code generators to a subdirectory Let's have a bit of organization here, rather than an ever-growing Meta folder. 2026-04-22 16:56:17 -03:00			`"generate_libjs_bytecode_def_derived.py"`
LibJS: Generate C++ bytecode instruction classes from a definition file This commit adds a new Bytecode.def file that describes all the LibJS bytecode instructions. From this, we are able to generate the full declarations for all C++ bytecode instruction classes, as well as their serialization code. Note that some of the bytecode compiler was updated since instructions no longer have default constructor arguments. The big immediate benefit here is that we lose a couple thousand lines of hand-written C++ code. Going forward, this also allows us to do more tooling for the bytecode VM, now that we have an authoritative description of its instructions. Key things to know about: - Instructions can inherit from one another. At the moment, everything simply inherits from the base "Instruction". - @terminator means the instruction terminates a basic block. - @nothrow means the instruction cannot throw. This affects how the interpreter interacts with it. - Variable-length instructions are automatically supported. Just put an array of something as the last field of the instruction. - The m_length field is magical. If present, it will be populated with the full length of the instruction. This is used for variable-length instructions. 2025-11-20 18:14:50 -03:00			`"${LIBJS_INPUT_FOLDER}/Bytecode/Bytecode.def"`
			`"Bytecode/Op.h"`
			`"Bytecode/Op.cpp"`
			`EXTRA_HEADER "Bytecode/OpCodes.h"`
			`arguments -i "${LIBJS_INPUT_FOLDER}/Bytecode/Bytecode.def"`
			`)`
			`endfunction()`