<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>compilers on Paul Piper</title><link>https://www.paul-piper.de/tags/compilers/</link><description>Recent content in compilers on Paul Piper</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>©Paul Piper</copyright><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.paul-piper.de/tags/compilers/index.xml" rel="self" type="application/rss+xml"/><item><title>What Bluespec Borrowed From Haskell</title><link>https://www.paul-piper.de/posts/bluespec-haskell-shared-grammar/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/bluespec-haskell-shared-grammar/</guid><description>Bluespec System Verilog reads like Haskell because it is, structurally, Haskell wearing a hardware costume. I ran into the consequence directly while building Bluespec support into Flexible Haskell.
Rules instead of always-blocks Write Verilog and you describe hardware behavior with always-blocks: procedural code triggered on a clock edge, and the burden of proving nothing collides sits entirely on you. Two blocks touching the same register in the same cycle is your bug to find, by hand, usually late.</description></item><item><title>The JVM Taught Us Tiered Compilation</title><link>https://www.paul-piper.de/posts/tiered-compilation-jvm-vs-julia/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/tiered-compilation-jvm-vs-julia/</guid><description>I spent fifteen years tuning JVMs for banks, retailers and insurers, and it took building a Julia plugin to notice how much of that tuning HotSpot does for you before you ever touch a flag.
The problem HotSpot solves is the one every JIT has: interpreted code starts instantly and runs slow, compiled native code starts slow and runs fast. You cannot have both from the first line. HotSpot&amp;rsquo;s answer, tiered compilation, has been the default since Java 7, and it works by never picking just one option.</description></item><item><title>Why a Language Plugin Needs a Grammar, Not a Regex</title><link>https://www.paul-piper.de/posts/bnf-grammar-jflex-language-plugin/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/bnf-grammar-jflex-language-plugin/</guid><description>A regex can highlight a language for about as long as nobody nests anything. The moment a string contains a comment marker, or a comment contains something that looks like a string, or a block comment nests inside another block comment the way Julia&amp;rsquo;s #= ... =# is allowed to, the pattern either lights up the wrong span or gives up entirely. A regex is the cheap first instinct for a language plugin, and it means you will rewrite the highlighter twice.</description></item></channel></rss>