7cb6be25 - Rebase, fix conflicts, and remove the bridge because it doesn't support the CLIF view (#10892)

Mon, 02 Jun 2025 16:43:25 +0000

Rebase, fix conflicts, and remove the bridge because it doesn't support the CLIF view (#10892)Auto-format explorer index.jsUse CRC24 to pick colors for offsets in exploreMake better use of the DOMIn the ASM view, instead of creating one element per instruction,create one per WASM chunk. This significantly reduces the amountof elements we have to take care of, including event listeners.For both views, get rid of all the maps to look up DOM elements byWASM offset and use CSS selectors to find them. This made thingsquite a bit smoother. To highlight items, we now add a class toelements with the same WASM offset, and remove it when we don'twant to highlight them anymore.In addition to this, use a bit more tricks to get brighter colorsfrom the CRC24 algorithm we're now using to pick the colors. (Sincethe colors can now be very dark, we get the luminance by using theNTSC color space, or YIQ, and use contrasting colors.)Draw polygon bridging WAT and ASM viewsScale luma calculation to a power of two to avoid integer divisionOutline hovered linesInstead of using opacity, which slow down rendering, use a solidoutline, which looks nicer and is more efficient!Adjust bridge width to account for different scrollbar widthsUse simpler math in rgbToLuma() to avoid multiplications tooSlight improvement to crc24 calculationDraw multiple conections from WAT to ASM viewsSometimes the ASM block contains disjoint sets of instructionsthat relate to one WASM instruction, so link all of them at thesame time.Show WASM offset on hover in the ASM viewFix grouping of ASM instructionsSome instructions with NULL wasm_offset were being group togetherwith the first instruction in the stream that had an offset.Only set the title attribute to show WASM offset on hoverThis saves quite a bit of memory!Fix grouping of instructions in ASM modeAdd note about the origin of the CRC-24 calculationTweak color generation (let some brighter colors pass the filter)Ensure we have enough elements to compute the bridge polygonI don't know why this happens, but sometimes, a block of instructionsin the ASM side, that have a WASM offset in the generated JSON, won'thave an equivalent in the WAT side. Guard against this.Don't obscure the hovered line with the outlineSimplify bridge width calculationOptimize hovering of blocks when one 1 WAT element matches with 1 ASM elementAddress review commentsMake eslint happySince this code runs in a browser, we need to tell eslint thatit's going to run in a browser enviroment so things like `window`and `document` are defined.Signed-off-by: L. Pereira Co-authored-by: L. Pereira List of files: /wasmtime-44.0.1/crates/explorer/package.json

8848bac2 - Add linting and formatting for JS code in `wasmtime explore` (#8675)

Tue, 21 May 2024 21:04:05 +0000

Add linting and formatting for JS code in `wasmtime explore` (#8675) List of files: /wasmtime-44.0.1/crates/explorer/package.json

Changes in package.json

7cb6be25 - Rebase, fix conflicts, and remove the bridge because it doesn't support the CLIF view (#10892)

8848bac2 - Add linting and formatting for JS code in `wasmtime explore` (#8675)