Re: CE DLL alignment.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

If I created a DLL for ~63.5 K, it really occupies 128K when it's
loaded? . Just tryin to clear that hang over :-)

It occupies ONLY the actual size of the DLL in physical memory, the system
allocates space in virtual memory for each DLL starting on a 64K boundary.
You really should not try to rely on the exact behaviour of this particular
aspect of the system as it's possible that different versions of the OS
behave differently. (e.g. the exact answer to your question is "UNDEFINED")
t's very likely that's not something that has changed over the past, nor
likely behavior that will change in the future but you shouldn't "bet the
farm" on it.)


.

Relevant Pages

  • Re: Delphi to take advantage of multiple threads within the compiler>
    ... address into any given function pointer - ergo if different processes need to map the dll to different addresses, they by definition cannot share the same physical memory image. ... Our applications now load noticeably faster, ...
    (borland.public.delphi.non-technical)
  • Re: BadImageFormatException on framework 64 bit
    ... Rudy wrote: ... If the application is developed yourself, you can set it in the development tools to mark it always running in 32 bit mode. ... Hence, overall the system still can take some advantage, e.g. the system can use more physical memory. ... the best solution is to convert the 32 bit DLL to 64 bit DLL. ...
    (microsoft.public.dotnet.framework)
  • Re: Do fork copies the "Code" Memory space?
    ... since I don't know for sure about DLL. ... >> in the same physical memory. ... > relocation table listing all instructions using absolute addresses ... Måns Rullgård ...
    (comp.unix.programmer)
  • Re: CE DLL alignment.
    ... When you load the dll won't it also allocate pages for process data for any data that isn't in shared data segments? ... It occupies ONLY the actual size of the DLL in physical memory, the system allocates space in virtual memory for each DLL starting on a 64K boundary. ... You really should not try to rely on the exact behaviour of this particular aspect of the system as it's possible that different versions of the OS behave differently. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Do fork copies the "Code" Memory space?
    ... Andrei Voropaev writes: ... since I don't know for sure about DLL. ... > in the same physical memory. ... relocation table listing all instructions using absolute addresses ...
    (comp.unix.programmer)