John Regehr on Nostr: if you look at what LLVM actually spends its time doing (and I assume probably also ...
if you look at what LLVM actually spends its time doing (and I assume probably also GCC?), it's pointer chasing. basic blocks are doubly linked lists, etc. for a while I've had the idea that a from-scratch compiler re-implementation for GPGPUs might work out pretty well. and if not, it would at least be a couple years of super fun hacking. anyhow somehow I only now ran across this:
"Compilation On The GPU? A Feasibility Study"
https://dl.acm.org/doi/pdf/10.1145/3528416.3530249Published at
2024-11-30 05:00:44Event JSON
{
"id": "ae4f88bc1be7cda870a0b781bdb0ad0155c3eef6f97a3266d23a874364f727f1",
"pubkey": "a1a4eb540235341a2db0d8a08cfb74edc4bb06b316c7bb39580c55559ce71ba1",
"created_at": 1732942844,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/regehr/statuses/113570142277473365",
"activitypub"
]
],
"content": "if you look at what LLVM actually spends its time doing (and I assume probably also GCC?), it's pointer chasing. basic blocks are doubly linked lists, etc. for a while I've had the idea that a from-scratch compiler re-implementation for GPGPUs might work out pretty well. and if not, it would at least be a couple years of super fun hacking. anyhow somehow I only now ran across this:\n\n\"Compilation On The GPU? A Feasibility Study\"\n\nhttps://dl.acm.org/doi/pdf/10.1145/3528416.3530249",
"sig": "b64011ee7f058c4aaf50a9c20a382da1dc0c858216ade9da8dbcb51f0413b0a57719806449fc443ba0e16f0176c5a0a1e3056dcbd44112c5edd666b87dcbb03e"
}