2 ms·
What would be the use-case for this? Most open source software is trivially portable across architectures. For the stuff that isn't there are code transformatio
by pabs3 5y ago
What would be the use-case for this? Most open source software is trivially portable across architectures. For the stuff that isn't there are code transformation tools like qemu-user-static.
- peter_d_sherman 5y agoYour argument is one of convenience, mine is one of education/understanding... Sure, one could use every computer program in existence without becoming a computer programmer and gain useful function from them, and this would not be wrong in any way -- but there are also those of us who wish to understand things at a very deep level... There are those of us who not only want to understand how computer programs work -- but how ISA's work, how the underlying hardware works, everything down to the substructures, the the adders, the logic gates, the flip-flops, the transistors, everything... And that list includes (but is not limited to!)... x86 microcode... Or more specifically, microcode in general...
- pabs3 5y agoI think it would be better to abandon x86 than to try to understand it :)
- frazbin 5y agoMost likely there are microcode bugs being quietly exploited by powerful actors. Documenting/reversing/auditing the code in public makes it more likely white hats will find these bugs and mitigate them.. which takes a little power away from these actors, or at least costs them a bit of money to find a replacement.. and there's always the chance you find a bug worth billions to the agency exploiting it. So while we may never know about it, this is a big deal.