Interesting bit from the docs here:
"Addresses near the 2-GB boundary are typically used by various system
DLLs. Therefore, a 32-bit process cannot allocate more than 2 GB of
contiguous memory, even if the entire 4-GB address space is available."
http://msdn.microsoft.com/en-us/library/bb613473%28v=VS.85%29.aspx
Maybe more fundamental changes are needed, such as the ability to change
the image's memory footprint dynamically.
On 4/23/11 17:34 , Andres Valloud wrote:
You can determine the switches better than me... for us, it was
/LARGEADDRESSAWARE, also a linker switch:
http://msdn.microsoft.com/en-us/library/wz223b1z.aspx
Now, keep in mind that expanding the address space capability of the app
doesn't mean Windows will give it 4gb. Under some Windows
configurations, that won't happen unless you change how Windows boots.
Under some versions, 4gb is just not possible. See here:
http://msdn.microsoft.com/en-us/library/aa366778%28v=VS.85%29.aspx
On 4/23/11 15:40 , Igor Stasenko wrote:
On 23 April 2011 21:48, Andres Valloud
<[email protected]> wrote:
Some seemingly useful items to start tracing through Google appear
here...
http://groups.google.com/group/gnu.gcc.help/browse_thread/thread/b1548cd5e7c15a8b/05628751f5f46111?pli=1
so we can add
'-Wl,--large-address-aware'.
option to linker.
