|What does 32 bit application mean? email@example.com (Jatin Bhateja, Noida) (2005-07-28)|
|Re: What does 32 bit application mean? Juergen.Kahrs@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2005-07-31)|
|Re: What does 32 bit application mean? DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2005-07-31)|
|Re: What does 32 bit application mean? firstname.lastname@example.org (Florian Weimer) (2005-08-01)|
|Re: What does 32 bit application mean? email@example.com (Marco van de Voort) (2005-08-03)|
|Re: What does 32 bit application mean? firstname.lastname@example.org (Marco van de Voort) (2005-08-05)|
|Re: What does 32 bit application mean? email@example.com (Andi Kleen) (2005-08-05)|
|From:||Marco van de Voort <firstname.lastname@example.org>|
|Date:||3 Aug 2005 01:23:18 -0400|
|Organization:||Stack Usenet News Service|
On 2005-08-01, Florian Weimer <email@example.com> wrote:
> Most operating systems supporting AMD64 do not currently offer such a
> choice, which is a bit disappointing. The extended register set would
> benefit ILP32 applications as well (which generally run faster because
> smaller pointers result in a smaller working set).
I also noted this. And it seems the AMD64 architecture indeed supports
it. Another advantage is simpler PIC support (one can move from EIP
in native mode, and not in x86 mode).
[No, on an AMD64 a process is either in long mode that has the extra
registers and address modes and 64 bit addresses, or in compatibility
more which is just like ia86 protected mode. You can't mix and match.
The comments I've seen say that the code savings from the extra
registers and IP-relative addressing about cancel out the code bloat
from the bigger pointers, but 64 bit apps still run slower because the
tools are less mature and so much code has been heavily optimized to
run fast on x86. -John]
Return to the
Search the comp.compilers archives again.