Win64 and LARGEADDRESSAWARE
- From: "Eric Twietmeyer" <notvalid@xxxxxxxxx>
- Date: Mon, 18 Apr 2005 11:45:13 -0700
"Gilles Vollant" <info@xxxxxxxxxxxx> wrote in message
news:ec4DFpIQFHA.1076@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> "Mike Roberts" <"miker at tulgagames dot com"> a écrit dans le message de
> news: OHGVPhIQFHA.1604@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> I've noticed in the AMD64 documentation that the linker has a
>> /LARGEADDRESSAWARE:[NO] option. Are addresses above 2G enabled by default
>> on this platform?
>
> yes, addresses above 2G are enabled by default on 64 bits platform
>
>
I have a further question on this topic. We have an AMD64 system in house,
we loaded the release candidate Windows XP 64Bit and created a couple of
small applications targeting 64Bit. We just compiled a small C app that
just called VirtualAlloc repeatedly and printed out how much memory we were
allowed to allocate. We were never able to get beyond 3Gb. And it was
necessary to specify the LARGEADDRESSAWARE option.
How is one supposed to get beyond 3Gb?
And I have read that running a 32bit app under WOW64 should allow it to grab
all 4GB of possible address space. When we do this with a standard 32bit
app and just allocate memory we are not able to get beyond 2Gb. Setting the
LARGEADDRESSAWARE flag in the pe file header allows us to get to 3GB, but in
no cases were were able to get all 4GB of memory.
Does anyone know what it is we might be doing incorrectly? Our application
is often bumping up against the 2GB address limit because of the size of the
data we must process. Telling our customers that they can buy an AMD64 or
an Intel EMT64 based processor and use the 64 bit OS from Microsoft would
give them 4Gb of virtual address space would be a big win for us.
Any pointers or information on this topic beyond what is in MSDN would be
very helpful.
Thanks,
-Eric Twietmeyer
.
- Follow-Ups:
- Re: Win64 and LARGEADDRESSAWARE
- From: Pavel Lebedinsky
- Re: Win64 and LARGEADDRESSAWARE
- Prev by Date: Re: Return value of BOOL (win32 api)
- Next by Date: FSCTL_MOVE_FILE +OVERLAPPED I/O
- Previous by thread: sendinput(): directx game will respond to all keys except escape
- Next by thread: Re: Win64 and LARGEADDRESSAWARE
- Index(es):
Relevant Pages
|
