delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/02/17/02:03:03

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: Optimizing memset/memcpy/strcpy/etc.
17 Feb 1998 02:03:03 -0800 :
Message-ID: <01BD3B8F.A9DF2EA0.cygnus.cygwin32.developers@gater.krystalbank.msk.ru>
Reply-To: cygwin32-developers AT cygnus DOT com
To: "'cygwin32-developers AT cygnus DOT com'" <cygwin32-developers AT cygnus DOT com>

Ian Lance Taylor wrote:
> Some of the posts on the gnu-win32 list have implied that Windows
> always relocates DLLs if they have relocation information.  I would
> hope that that is not true--if the DLL is loaded at the image address,
> it should not be relocated.  Does anybody know exactly what Windows
> does?  Perhaps there is something incorrect about the DLLs which

It seems to me not true. Windows (at least NT) relocates a dll only if 
address space is in use by any other dll/stack/program code/alloced memory. 
But dll reallocation is not only slowness of process startup, another one 
is linking of application/dll imports/exports - it's really slow process - 
for every import loader performs a binary search of corresponding dll's 
export by name.

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019