<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Arch on Daniel Hacks It</title>
    <link>https://danielhacks.it/tags/arch/</link>
    <description>Recent content in Arch on Daniel Hacks It</description>
    <generator>Hugo -- 0.147.5</generator>
    <language>en</language>
    <lastBuildDate>Fri, 24 Jul 2026 10:16:21 +0200</lastBuildDate>
    <atom:link href="https://danielhacks.it/tags/arch/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Single Cycle RISCV32I Datapath</title>
      <link>https://danielhacks.it/blog/20260724_single_cycle_riscv_datapath/</link>
      <pubDate>Fri, 24 Jul 2026 10:16:21 +0200</pubDate>
      <guid>https://danielhacks.it/blog/20260724_single_cycle_riscv_datapath/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Perhaps it&amp;rsquo;s only me, but I believe anyone who is serious at digital design should at least try to implement a simple processor. This is the first of a series aimed to end with a usable processor for my projects, in an attempt to learn some of the concepts of computer architecture, while at the same time honing my hardware design skill. This post is a technical overview of the design choices behind it: where I made reasonable calls, where I got it wrong, and what I learned along the way.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
