pastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 3 months agoSome Mnemonicssh.itjust.worksimagemessage-square20fedilinkarrow-up1340
arrow-up1340imageSome Mnemonicssh.itjust.workspastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 3 months agomessage-square20fedilink
minus-square9point6@lemmy.worldlinkfedilinkarrow-up26·3 months agoI still don’t know why this architecture went for a Double XOR as the NOP, I guess they were just flexing that the reference chip design could do both in a single cycle
minus-squarepancake@lemmygrad.mllinkfedilinkarrow-up3·3 months agoWhen returning from kernel code, one should issue Drop Execution Ring Privileges, of course.
I still don’t know why this architecture went for a Double XOR as the NOP, I guess they were just flexing that the reference chip design could do both in a single cycle
When returning from kernel code, one should issue Drop Execution Ring Privileges, of course.