News for hackers. Stuff that matters.
Re:Decompiling a Nintendo 64 Game in 84 Days by Sesse__ on Thursday August 27, 2026 @04:11PM (#49470556)
> Historically there was a notion of "clean room" reimplementation

These projects start off with the original assembly code and use it actively throughout all stages. This is about as far away from clean room as you get.

Re:Decompiling a Nintendo 64 Game in 84 Days by jonhohle on Thursday August 27, 2026 @08:09PM (#49472843)
These projects do not start with assembly. They start with machine code interleaved with data. Even getting to assembly through a disassembled requires some input and understanding. Usually these are raw binaries with no (or limited) metadata.

When run through a disassembler, in most cases, it’s probably the first time anyone has ever looked at the assembly (assuming PlayStation or newer). There are no comments or labels or symbols. Not what most people would consider “the original assembly”.

Re:Decompiling a Nintendo 64 Game in 84 Days by xyzsparetimexyz on Thursday August 27, 2026 @09:13PM (#49473240)
Ghidra is able to figure out the functions in around 99%++ of cases though
Re:Decompiling a Nintendo 64 Game in 84 Days by S-E-P on Friday August 28, 2026 @12:46AM (#49474466)
The term "original assembly code" is sufficient enough to communicate that the binaries that are being reversed are what is disclosed to the public intentionally.

Their comment still stands; whether it's machine code or "original assembly code" that shipped on the disk it falls under "clean room" reversing and by extension implementation.

Re:Decompiling a Nintendo 64 Game in 84 Days by circuit10 on Friday August 28, 2026 @08:25AM (#49477531)
Being available to the public if they bought the game doesn't mean it's in the public domain and you're allowed to upload a copy of it (or a derivative work) onto GitHub, though

(I like these projects but I really don't think they could defend themselves legally if you company went after them)