The first two instructions looked legitimate, but the third looked unlikely to be a real instruction.
Given that the first appears to be a branch, that's not surprising. When disassembling, not following the flow will likely not give you anything meaningful. If the author is reading this: have you tried Ghidra?
That said, this seems a lot simpler than PC BIOSes in structure, as the latter are usually written in a combination of C and Asm (I can see why no one wanted to write MIPS Asm) and are self-extracting compressed archives.
Not even sure that's true anymore. How else to explain WSL/WSL2? They practically lead you to Linux by the hand these days.
Or you know, just didn't get hung up on the blatantly obvious thing not being explicitly disclaimed right in the title, only in the preamble?
Literal second sentence in the article, in case it wasn't incredibly obvious to people anyways:
> It supports a subset of C that is large enough to write real and interesting programs.
I'm all for more boring headlines, but this characterization is ridiculous.
(As for PowersHell... yuck. It's like MS decided to reinvent bash but in the most bureaucratic and obfuscated way they could.)
Dead Comment
Dead Comment
Seeing "== false" and variations thereof always triggers the suspicion that its author doesn't fully understand boolean expressions. I have once seen the even worse "(x == false) == true".