name your function as malloc() and see to world burn and generate bugs at factorial rate.

volatile int blackhole;
blackhole = 1;
const int X = blackhole;
const int Y = blackhole;

Compiler is forbidden to assume that X == 1 would be true. It’s also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> “read only volatile value at read only address hwreg”. Compiler can assume the hwreg address won’t magically change, but can’t assume the value read from that address won’t.

I think the difference with Dolphin is that it now emulates an extinct system(s), so it cannot possibly compete with the actual thing. They did have a close call last year, if I remember, and they pretty quickly went into “jettison all illegal shit out of the code base NOW.” -mode.

I had a similar debacle, when I managed to corrupt a btrfs file system to point it wouldn’t mount again…

I was preparing it to have as my main system on bare hardware. I had accidentally mounted the same block device simultaneously in the host and guest: kablamo silent corruption and all 5 hours of progress lost.^* :(

*shred the guest VM, host was ok.

On arch, UEFI boot vars are mounted at /sys/firmware/efi/efivars. It’s unwise to rm -rf them…

GameBoy Color with a single game: Pokémon Red.

Next time I was able go to the shop they had upgraded to GameBoy Advance and no GB/GBC games were to be never found again. It was the best/worst thing I ever got. :'(