Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Hyrum’s Law reaching all the way down to the instruction decoder. And for those who care the ud2 opcode is 0F 0B
    by arkj
  • It's sad that this is probably going to become canon, now, Raymon Chen being as influential as xe is, when what actually happened was that in 1998 H. Peter Anvin saw UD2 in Intel's doco, and that there was a second opcode that was just described by Intel as merely undefined, so gave it the mnemonic UD1 in the 0.98p3-hpa version of NASM because 'calling it UD1 seemed to make sense'.

    * https://groups.google.com/g/comp.lang.asm.x86/c/ErG5TJEDjiw/...

    * https://github.com/netwide-assembler/nasm/blob/nasm-0.98.x/C...

    by JdeBP
  • I'm not much of an x86 person but on other architectures you can raise software interrupts/exceptions. Does x86 not have this or did those facilities not cover enough use cases?
    by Neywiny
  • Though, for whatever reason, the instruction internally decoded as if it took two parameters, a register destination and a register-or-memory source.

    Because the rest of the 0F Fx line also has a ModRM. Ditto for 0F Bx.

    So if your 0F FF is at the end of a page, and the next page is not present, you sometimes got an invalid opcode exception and you sometimes got an access violation.

    This reminds me of some related information on instruction length and decoding of "undefined" instructions I have filed away from a long time ago; sadly this stuff is disappearing from the Internet, but both the Archive and I still remember:

    https://web.archive.org/web/20160721202526/http://pferrie.ho...

    Such information is very important for emulation accuracy and some security contexts.

    by userbinator
  • Tangential, but I almost never read assembly [1], but I do read Java bytecode pretty frequently, primarily because doing that can sometimes be a good substitute for benchmarking [2], which I do not enjoy.

    The thing that never seems to stop tripping me up is the different “dup” codes that compile. At some point I really need to properly learn the difference between dup_x2 and dup2_x1 and dup2_x2.

    [1] not out of like an ethical objection, just my career has involved almost no reverse engineering and it’s also never been a path I have been super interested in to pursue on my own.

    [2] e.g. if two competing chunks of code emit the same bytecode, you don’t need to pull out JMH. My go to example for this is using if statements vs switches, which will usually emit the same code so performance arguments are moot.

    by tombert
  • Nowadays UD0 UD1 UD2 are in the SDM and APM.

    We also got UDB (D6), the one-byte variant that arrived with x86-64 for 64-bit mode.

    And we have always had UDW (FF FF), aka group #5 (1st FF) with a modrm byte of mod=11b r/m=111b (/7) reg=111b (2nd FF) -- that one matters for memory with all bits set to 1, or for buses terminated to all 1 when no device claims an access.

    by 349ru3h4f03
  • Thus finally the 0F FF believers were rewarded by being give the honor of op code UD0 making it the one and true original invalid opcode permanently disgracing the 0F B9 adherents with the shame of UD1.
    by hacker_homie
  • > Better to stick with ud2. Its behavior is consistent and architecturally guaranteed.

    Ah, finally an undefined instruction whose behaviour is consistent and architecturally guaranteed!

    by boramalper

Explore Birbla archives