<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cage: Hardware-Accelerated Safe WebAssembly · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2408.11456/</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/2408.11456/feed.xml" rel="self" type="application/rss+xml" /><item><title>Cage: Hardware-Accelerated Safe WebAssembly — mentioned by westurner</title><link>https://news.ycombinator.com/item?id=46151269</link><guid isPermaLink="false">urn:hackerpapers:mention:2408.11456:46151269</guid><pubDate>Thu, 04 Dec 2025 18:46:49 GMT</pubDate><description>&lt;p&gt;&amp;quot;Cage: Hardware-Accelerated Safe WebAssembly&amp;quot; (2024) https://arxiv.org/abs/2408.11456v2 : &amp;gt; Abstract: WebAssembly (WASM) is an immensely versatile and increasingly popular compilation target. It executes applications written in several languages (e.g., C/C++) with near-native performance in various domains (e.g., mobile, edge, cloud). Despite WASM&amp;#x27;s sandboxing feature, which isolates applications from other instances and the host platform, WASM does not inherently provide any memory safety guarantees for applications written in low-level, unsafe languages. &amp;gt; To this end, we propose Cage, a…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2408.11456/"&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>Cage: Hardware-Accelerated Safe WebAssembly — HN submission</title><link>https://news.ycombinator.com/item?id=46151170</link><guid isPermaLink="false">urn:hackerpapers:submission:2408.11456:46151170</guid><pubDate>Thu, 04 Dec 2025 18:39:47 GMT</pubDate><description>&lt;p&gt;Cage: Hardware-Accelerated Safe WebAssembly&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 2 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2408.11456/"&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>Cage: Hardware-Accelerated Safe WebAssembly — mentioned by westurner</title><link>https://news.ycombinator.com/item?id=46125171</link><guid isPermaLink="false">urn:hackerpapers:mention:2408.11456:46125171</guid><pubDate>Tue, 02 Dec 2025 19:05:35 GMT</pubDate><description>&lt;p&gt;A bit OT here, but oh well Would hardened_malloc or llvm scudo be useful in a WASM runtime (given that WASM doesn&amp;#x27;t have an MMU)? https://www.google.com/search?q=would+hardened_malloc+be+use... Emscripten handles malloc and free with dlmalloc, emmalloc, mimalloc, emcc your_code.c -s &amp;#x27;MALLOC=&amp;quot;emmalloc&amp;quot;&amp;#x27; -o your_code.html how to add &amp;quot;hardened_malloc&amp;quot; memory allocator support to emscripten for WASM? https://www.google.com/search?q=how+to+add+%22hardened_mallo... &amp;quot;Import custom memory manager?&amp;quot; · Issue #24851 · emscripten-core/emscripten https://github.com/emscripten-core/emscripten/issues/24851…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2408.11456/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
