Re:Loading an x64 register, how hard could it be?
by 0xcde4c3db on Saturday September 19, 2015 @11:20PM
(#10246464)
It's not crazy at all. This sort of shuffling is pretty standard for RISC ISAs, where it's typical to have fixed-length instructions that are no larger than the registers.
For example, MIPS has no actual "load immediate" instruction. Instead, say you want to load the value 0x12345678 into register t0. You can go ahead and tell your MIPS assembler:
li $t0, 0x12345678
but it will actually emit something like: lui $t0, 0x1234
ori $t0, $t0, 0x5678
"lui" here is the "load upper immediate" instruction, which loads the target register with the 16-bit immediate, left-shifted by 16 bits. "ori $t0, t0, 0x5678" then performs a bitwise OR with its immediate to get the lower 16 bits into the register. This can be done in a single instruction if the immediate is 16 bits or smaller by using the dedicated zero register (a read-only register that always contains 0x00000000, which turns out to be extremely handy for minimizing an instruction set): ori $t0, $zero 0xabcd
Re:Loading an x64 register, how hard could it be?
by JoshTriplett on Sunday September 20, 2015 @12:52AM
(#10246598)
SPARC does something similar, with a special "sethi" instruction to set the high 22 bits of a register, using more space for an argument than any other instruction does.
Some architectures manage to do something more clever than that, as well. See http://alisdair.mcdiarmid.org/arm-immediate-value-encoding/ for instance.
Re:Loading an x64 register, how hard could it be?
by pm215 on Sunday September 20, 2015 @05:00AM
(#10246969)
The SPARC call instruction beats that with a 30 bit immediate, sacrificing a huge chunk of the encoding space for being able to reach any target in a 32 bit address space with a single instruction.
Re:Loading an x64 register, how hard could it be?
by userbinator on Sunday September 20, 2015 @12:56AM
(#10246602)
I think the author is saying what's crazy is the lack of 64-bit immediates in a machine that contains 64-bit registers. There's an instruction to add a 32-bit immediate (and I believe 8 and 16 as well), but not a 64-bit one.
Re:Loading an x64 register, how hard could it be?
by devit on Sunday September 20, 2015 @04:06AM
(#10246902)
It's rare for programs to contain integer constants that don't fit in 32 bits, and they aren't needed for 64-bit code/global memory references due to the introduction of addressing relative to the instruction pointer.
Also there is a 15 bytes instruction length limit that would have to be extended if 64-bit immediates were allowed on all instructions.
Re:Loading an x64 register, how hard could it be?
by hrydgard on Sunday September 20, 2015 @04:26AM
(#10246933)
No processor out there has 64-bit arithmetic immediates - it's not useful enough in practice that you'd want it, and most other architectures have fixed-length 4-byte instructions anyway so it's not practical.
Re:Loading an x64 register, how hard could it be?
by pcwalton on Sunday September 20, 2015 @01:47AM
(#10246682)
It's not crazy: it's just standard operating procedure for RISC-like architectures. In fact, anything that brings the x86 architecture closer to RISC is nice in my book.
Re:Loading an x64 register, how hard could it be?
by TheCondor on Sunday September 20, 2015 @08:59AM
(#10247347)
Alpha had all sorts of exotic load intermediate and shift instructions to help with this. 64bit registers, 32bit instructions, I forget the exact number but you only had 20ish bits of immediate value.
It seemed like slightly more of a chore then, with x8664 you can use memory with a lot of instructions..
I don't really think this is as crazy as the article is implying.