From:	cgf AT bbc DOT com (Christopher Faylor)
Subject:	Re: Optimizing memset/memcpy/strcpy/etc.
17 Feb 1998 14:38:32 -0800 :
Message-ID:	<EoJnnG.6nn.cygnus.cygwin32.developers@bbc.com>
References:	<01BD3B8F DOT A9DF2EA0 AT gater DOT krystalbank DOT msk DOT ru>
Reply-To:	cygwin32-developers AT cygnus DOT com
To:	cygwin32-developers AT cygnus DOT com

In article <199802171723 DOT MAA29244 AT subrogation DOT cygnus DOT com>,
Ian Lance Taylor  <cygwin32-developers AT cygnus DOT com> wrote:
>The import table in an executable or DLL has an ordinal hint field.
>The Windows loader is supposed to use that first when looking up the
>symbol in the DLL export table.  Comparing the hint fields I find in a
>binary linked against the cygwin DLL against the export symbol table,
>both as printed by objdump -p, I find that they don't match.  The
>numbers in the hint field are not the export symbol numbers.

Maybe I'm missing something, this is also the case using Microsoft
tools.  I just used 'dumpbin' to print out the table of a .exe produced
by MSDEV.  I don't see any correspondence between the numbers.  The
numbers produced by dumpbin seem to correspond to those produced by
objdump.

Are the hints numbers provided in the .lib stubs for the libraries somehow?
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."

- Raw text -