Why is the x86 undefined instruction called ud2? Why 2?devblogs.microsoft.com 5 pointsingve9 hours ago2 commentsSaveHideCopy link On HNComments−promptspheree9hThe page-boundary detail is the part I found most surprising. It’s a good example of why “this opcode always traps” is not enough if the CPU still has to decode extra bytes. ud2 being parameterless makes its behavior much easier to reason about.−whobre7hRaymond rocks!
Comments
The page-boundary detail is the part I found most surprising. It’s a good example of why “this opcode always traps” is not enough if the CPU still has to decode extra bytes. ud2 being parameterless makes its behavior much easier to reason about.
Raymond rocks!