This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: i386: Problems with references to import symbols.

From: Richard Henderson <rth at redhat dot com>
To: Dave Korn <dave dot korn at artimi dot com>
Cc: "'Kai Tietz'" <Kai dot Tietz at onevision dot com>, "'GCC Development'" <gcc at gcc dot gnu dot org>
Date: Wed, 21 Mar 2007 09:27:18 -0700
Subject: Re: i386: Problems with references to import symbols.
References: <OF1EF35129.C3E0D0CC-ONC12572A5.004271A7-C12572A5.0042FB66@onevision.de> <20070321160926.GA30824@redhat.com> <009c01c76bd4$438d9720$2e08a8c0@CAM.ARTIMI.COM>

On Wed, Mar 21, 2007 at 04:16:20PM -0000, Dave Korn wrote:
>   Presumably there would be no problem in just waiting until runtime to
> initialise the my_malloc_hook variable dynamically instead of trying to
> statically initialise it?

Dunno.  One could also wait to expand *__imp_foo, for functions,
until expanding the function call.  And then this variable would
receive the address of the import library thunk.

What does VC++ do?  I'm mostly wondering about what pointer 
equality guarantees we can make.

r~

Follow-Ups:
- RE: i386: Problems with references to import symbols.
  - From: Danny Smith

References:
- i386: Problems with references to import symbols.
  - From: Kai Tietz
- Re: i386: Problems with references to import symbols.
  - From: Richard Henderson
- RE: i386: Problems with references to import symbols.
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]