The AArch64 processor (aka arm64), part 2: Extended register operations
There are a number of places where the instruction set permits the value in a register to be transformed before it is used. The set of valid transforms vary from instruction to instruction, but they share a common syntax.
|Shifted||Logical shift left.|
|Logical (unsigned) shift right.|
|Arithmetic (signed) shift right.|
|Extended||Unsigned||extend low byte||shifted left.|
|Unsigned||extend low halfword||shifted left.|
|Unsigned||extend low word||shifted left.|
|Unsigned||extend low doubleword||shifted left.|
|Signed||extend low byte||shifted left.|
|Signed||extend low halfword||shifted left.|
|Signed||extend low word||shifted left.|
|Signed||extend low doubleword||shifted left.|
ASR transformations are formally known as shifted registers. They take a value in a register and shift it.
The extend+shift transformations are formally known as extended registers. They extract a subset of the source register, extend it either as a signed or unsigned value to the full operand size, and then shift the extended result.
Shifting the zero register isn’t particular useful since you still get zero, but the instruction encoding lets you do it. Similarly, there is no practical difference between
SXTX (unsigned and signed extension of the low doubleword of a 64-bit register) since the low doubleword of a 64-bit register is the whole register.
For extended registers, the assembler lets you omit the shift amount, in which case it defaults to zero. The shift amount is not optional for the shifted registers.
Before you get all excited about the possibilities, know that not all instructions support all of these transformations, and for the ones that they do, the shift amounts are limited. We’ll look at the restrictions as they arise. For now, I just wanted to introduce the concepts.
As a convenience, if you are using an instruction that accepts only extended registers, but you want to use a
LSL, you can write
LSL #n, and the assembler will autoconvert it to
UXTW #n or
UXTX #n, depending on the operand size.
Next time, we’ll start putting these transforms to use when we look at addressing modes.
DirectUIHWND vs SysListView32
Off-topic and my apologies for that but I have no other choice.
After unsuccessfully scouring the net I still need to know what
method I should use to replace the list-view macro ListView_GetHotItem
when the control is a DirectUIHWND.
With best wishes.
DUI is undocumented. If you are trying to manipulate the desktop or file list in Explorer, use IShellWindows, IFolderView, etc.
Yes thank you, in the meantime I found the following lead from the old MSDN journals.
”To build this extension you need to create a COM inproc server that implements
IQueryInfo and IPersistFile.
IQueryInfo is required to provide the runtime text to the shell.
IPersistFile is used by Explorer to let the extension know about the specific file currently under the