<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Whose baseline compiler is it anyway? · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2305.13241/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2305.13241/feed.xml" rel="self" type="application/rss+xml" /><item><title>Whose baseline compiler is it anyway? — HN submission</title><link>https://news.ycombinator.com/item?id=39703474</link><guid isPermaLink="false">urn:hackerpapers:submission:2305.13241:39703474</guid><pubDate>Thu, 14 Mar 2024 13:08:14 GMT</pubDate><description>&lt;p&gt;Show HN: WebAssembly Instrumentation in the Wizard Research Engine&lt;/p&gt;&lt;p&gt;Hello all, I&amp;#x27;ve been working on research tools for Wasm for some time now, and just today we put up the pre-print for our newest paper &amp;quot;Flexible Non-intrusive Dynamic Instrumentation for WebAssembly&amp;quot; (https://arxiv.org/abs/2403.07973), which will appear in ASPLOS 2024. Two previous papers, one about Wizard&amp;#x27;s interpreter (https://dl.acm.org/doi/10.1145/3563311) and one about the JIT (https://arxiv.org/abs/2305.13241) have been discussed on HN before. This new paper explains what Wizard is really about: dynamic instrumentation of Wasm programs, without modifying the program or its behavior.…&lt;/p&gt;&lt;p&gt;7 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2305.13241/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Whose baseline compiler is it anyway? — mentioned by titzer</title><link>https://news.ycombinator.com/item?id=38272060</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.13241:38272060</guid><pubDate>Wed, 15 Nov 2023 01:01:56 GMT</pubDate><description>&lt;p&gt;Nice work! JIT compilers are a multi-dimensional tradeoff space: memory consumption, startup time, and execution time. I&amp;#x27;ve been experimenting with different ways of visualizing these three dimensions in a tradeoff space. I like the iteration time over time (showing warmup time) but that graph takes a lot of space and is necessarily per-benchmark (and only works with benchmarks with clearly repeated iterations). In my recent JIT paper I went for a scatter plot of two dimensions (setup time and code quality). It&amp;#x27;s here if anyone&amp;#x27;s curious: https://arxiv.org/abs/2305.13241&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.13241/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Whose baseline compiler is it anyway? — HN submission</title><link>https://news.ycombinator.com/item?id=36087455</link><guid isPermaLink="false">urn:hackerpapers:submission:2305.13241:36087455</guid><pubDate>Fri, 26 May 2023 17:49:28 GMT</pubDate><description>&lt;p&gt;Whose Baseline (compiler) is it anyway?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2305.13241/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Whose baseline compiler is it anyway? — HN submission</title><link>https://news.ycombinator.com/item?id=36079389</link><guid isPermaLink="false">urn:hackerpapers:submission:2305.13241:36079389</guid><pubDate>Fri, 26 May 2023 03:19:05 GMT</pubDate><description>&lt;p&gt;Whose baseline (compiler) is it anyway?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;28 points; 6 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2305.13241/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
