https://dciabrin.net/enContents © 2026 <a href="mailto:damien.ciabrini@gmail.com">Damien Ciabrini</a> Wed, 28 Jan 2026 23:18:47 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://dciabrin.net/posts/make-the-most-of-compiled-c-loops-on-the-68000/make-the-most-of-compiled-c-loops-on-the-68000/Damien Ciabrini<div><p>The other day I was working on my pet project <a href="https://github.com/dciabrin/ngdevkit">ngdevkit</a>, an open source C development kit for the <a href="https://en.wikipedia.org/wiki/Neo_Geo">Neo Geo</a> hardware. I needed to write a simple <code>clear_screen</code> function, and I chose to do it in C for simplicity, in the hope that this would get efficiently compiled into 68000 assembly. That apparently innocuous task led me to some interesting findings regarding gcc, binutils, and how you can hint the compiler to generate efficient 68000 code for small loops to reclaim some of your precious clock cycles.</p> <p><a href="https://dciabrin.net/posts/make-the-most-of-compiled-c-loops-on-the-68000/make-the-most-of-compiled-c-loops-on-the-68000/">Read more…</a> (13 min remaining to read)</p></div>68000neogeongdevkithttps://dciabrin.net/posts/make-the-most-of-compiled-c-loops-on-the-68000/make-the-most-of-compiled-c-loops-on-the-68000/Mon, 15 Sep 2025 17:07:49 GMT