<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: shuklaayush</title><link>https://news.ycombinator.com/user?id=shuklaayush</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 08 Aug 2026 07:25:02 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=shuklaayush" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by shuklaayush in "Pushing the limits of RISC-V emulation"]]></title><description><![CDATA[
<p>Author here, thanks for all the comments, didn't expect this to get picked up.<p>I've been working on speeding up RISC-V emulation for work and wrote this up as I went. Still learning this space, so I'd be keen to hear from people who've worked on emulators or binary translation, especially where you think this approach falls short</p>
]]></description><pubDate>Thu, 06 Aug 2026 09:24:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=49194429</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49194429</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49194429</guid></item><item><title><![CDATA[New comment by shuklaayush in "Pushing the limits of RISC-V emulation"]]></title><description><![CDATA[
<p>Neat, I guess this gets you the same output as a per-instruction translator without having to run an assembler and linker over the whole program. I should try this and add it to the post for completeness</p>
]]></description><pubDate>Thu, 06 Aug 2026 09:19:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=49194397</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49194397</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49194397</guid></item><item><title><![CDATA[New comment by shuklaayush in "Pushing the limits of RISC-V emulation"]]></title><description><![CDATA[
<p>Yeah, I went back and forth on the title. It's definitely not an interpreter. I still think of emulation as the umbrella term though, running code for one architecture on another, with interpretation and dynamic/static recompilation being different ways to get there</p>
]]></description><pubDate>Thu, 06 Aug 2026 09:05:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=49194296</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49194296</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49194296</guid></item><item><title><![CDATA[New comment by shuklaayush in "Pushing the limits of RISC-V emulation"]]></title><description><![CDATA[
<p>Hey, author here. That's fair, I didn't have the background. I knew interpreters would be slow, I just didn't expect it to still be ~10x after all the optimizations. After reading about it more though, that does seem to be the norm</p>
]]></description><pubDate>Thu, 06 Aug 2026 09:03:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=49194272</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49194272</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49194272</guid></item><item><title><![CDATA[New comment by shuklaayush in "Pushing the limits of RISC-V emulation"]]></title><description><![CDATA[
<p>I’ve been working on speeding up RISC-V emulation for my work, and I wrote a detailed blog about my learning. For some benchmarks, it now reaches roughly 85% of equivalent native throughput on an Apple M3.<p>I’d appreciate feedback from people who have worked on emulators, binary translation, JIT/AOT compilers.</p>
]]></description><pubDate>Thu, 30 Jul 2026 13:15:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=49109558</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49109558</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49109558</guid></item><item><title><![CDATA[Pushing the limits of RISC-V emulation]]></title><description><![CDATA[
<p>Article URL: <a href="https://shuklaayu.sh/blog/riscv-recompiler">https://shuklaayu.sh/blog/riscv-recompiler</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49109557">https://news.ycombinator.com/item?id=49109557</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Thu, 30 Jul 2026 13:15:51 +0000</pubDate><link>https://shuklaayu.sh/blog/riscv-recompiler</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49109557</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49109557</guid></item><item><title><![CDATA[Pushing the limits of RISC-V emulation]]></title><description><![CDATA[
<p>Article URL: <a href="https://shuklaayu.sh/blog/riscv-recompiler">https://shuklaayu.sh/blog/riscv-recompiler</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49099904">https://news.ycombinator.com/item?id=49099904</a></p>
<p>Points: 57</p>
<p># Comments: 35</p>
]]></description><pubDate>Wed, 29 Jul 2026 16:48:56 +0000</pubDate><link>https://shuklaayu.sh/blog/riscv-recompiler</link><dc:creator>shuklaayush</dc:creator><comments>https://news.ycombinator.com/item?id=49099904</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49099904</guid></item></channel></rss>