Thorsten Glaser wrote:
Dixitur illum ih8mj@fjf.gnu.de scribere...
That's already bad. Even worse if it can only read/write 64 bit words, so in particular 32 bit writes get quite cumbersome. (Do you know if this is so?)
x86 has never been like this, and FWIW the instruction set is still optimized for 32-bit operations,
BTW, I was referring to memory writes. I hope you too.
even in 64-bit mode (eg, a .intel_syntax noprefix .code32 add ax,1 will not change the high 16 bit of eax, but a .code64 add eax,1 will set the high 32 bit of rax to 0).
OK, then it may not be so bad WRT efficiency.
The main argument for a change is that with 32 bit `Integer', e.g. a schema (n: Integer) = array [1 .. n] ... will be more limited than necessary, and that's the biggest form in EP.
The main argument against it is compatibility, of course.
(continued in next mail)
Reference: www.amd.com -> manuals -r--r--r-- 1 tg tg 3019773 Oct 13 2003 AMD64 Architecture Programmer's Manual Volume 1: Application Programming.pdf -r--r--r-- 1 tg tg 4261489 Oct 13 2003 AMD64 Architecture Programmer's Manual Volume 2: System Programming.pdf -r--r--r-- 1 tg tg 4659928 Oct 13 2003 AMD64 Architecture Programmer's Manual Volume 3: General-Purpose and System Instructions.pdf -r--r--r-- 1 tg tg 2696640 Oct 13 2003 AMD64 Architecture Programmer's Manual Volume 4: 128-Bit Media Instructions.pdf -r--r--r-- 1 tg tg 2470923 Oct 13 2003 AMD64 Architecture Programmer's Manual Volume 5: 64-Bit Media and x87 Floating-Point Instructions.pdf
Thanks, for whom it may concern. Unfortunately I don't have the time to read some 15 MB of PDF files just for one processor's `Integer' type ...
Frank