Re: Windows array allocation problem

Steve Lionel wrote:
On Sep 29, 10:20 am, "James Van Buskirk" <not_va...@xxxxxxxxxxx>
wrote:

Windows does this just to torture you. If you can switch to x64, the
problems may abate temporarily:

Do keep in mind that Windows still has a 2 GB limit for static code
and data. This means that you cannot simply declare a large array in
common or as a local array on an x64 system. Dynamic allocation is the
only way to exceed the 2 GB boundary.

And, at the moment, I'm not able to even get within 350 MB of the 2 GB boundary. And I don't know why.

Roy Lewallen
.

Relevant Pages

  • Re: About c++ pointer
    ... Here you declare a local array and initialise it to "Hello world". ... > char *GetString2 ... Here you declare a pointer which points to a constant static area containing ...
    (comp.lang.cpp)
  • Re: Event Handle scope.
    ... Macca wrote: ... 'this' pointer) so it can access such shared variables. ... can declare a local array, copy the shared handles into it, and ...
    (microsoft.public.vc.mfc)
  • Re: How to test for the existence of __func__?
    ... as a local array inside each function. ... So if you're lucky the ... compiler may not declare it outside the function, ... Of course it's non-portable to declare your own identifier ...
    (comp.lang.c)