Comment on What’s the best method for documenting a ROM that I’m reverse-engineering?
CanadaPlus@lemmy.sdf.org 3 days agoHmm. Isn’t there a theorem that every combination of GOTOs is equivalent to some structured programming equivalent?
Comment on What’s the best method for documenting a ROM that I’m reverse-engineering?
CanadaPlus@lemmy.sdf.org 3 days agoHmm. Isn’t there a theorem that every combination of GOTOs is equivalent to some structured programming equivalent?
ch00f@lemmy.world 3 days ago
Thanks for the response!
I think the issue is that the “structured programming equivalent” is just a really, really long function that’s not any easier to read.
CanadaPlus@lemmy.sdf.org 3 days ago
Ah, here we go!
Do you have any idea what the high-level language in question might be? There has to be some logic to it (or alternatively it was spaghetti code as written). Even just the era and platform would narrow it down a bit.
ch00f@lemmy.world 3 days ago
Yeah, it was a budget portable device released in 1995 running a processor from 1984. I think it was just written in straight assembly. I’ve even found some unreachable code snippets in the assembly that print debug messages which confirm that theory.
CanadaPlus@lemmy.sdf.org 3 days ago
Yikes!
Yeah, I don’t think I can help too much with that. I hear there was quite an art to annotating hand-written assembly (to the point where you’re basically play-acting an interpreter or compiler), but I wasn’t there to learn.