There's so much good content in here, it's a shame you sandblasted your writeup with AI. "To the verifier, it is a number with a biography" is where I veered off the road and into a culvert.

▲

ayles 4 hours ago | parent | next [-]

Yes, there is a language barrier. And I was in a hurry because of ongoing life events, so it was kinda "today or in a month" for me. Couldn't keep it much longer for myself and wanted to share.

▲

MisterTea 34 minutes ago | parent | next [-]

If what you wrote here are your own words then I would say that you write well enough to not need an LLM.

	▲	ayles 31 minutes ago \| parent [-]
		That is actually quite reassuring, thanks

▲

tptacek 3 hours ago | parent | prev [-]

I totally understand where you're coming from. I'd recommend just publishing in your own words even if English isn't your best language; at this point, in 2026, it will read as charming and genuine, not slapdash.

A big problem with current model AI writing is that the topic sentence of every paragraph reads like a magazine headline, and it can be tricky to catch because a lot of magazine headlines are kind of good --- when they're headlines!

Number with a biography, yeesh. :)

This was neat work, though. Thanks for sharing!

	▲	ayles 3 hours ago \| parent [-]
		Noted for the future. I actually wrote a draft myself and mostly used ai to translate it. And there were some "late discoveries" that required me to patch article fast. For instance, for older memory tier (without arenas) I was using 2MB+8B regions with 8B overlap - this allowed unaligned reads to happen without checks, but later I got 4MB non-overlapping regions with llvm read-write alignments to work and that allowed me to remove additional check on stores, make memory fully writable from host side and made atomics correct. So this kind of patch needed to land in article between my "finishing tinkerings".

▲

rvz 4 hours ago | parent | prev [-]

Damn. That is a real shame. This whole writeup has some slop in it then.