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]

Re: linking of inline static methods

To: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
Subject: Re: linking of inline static methods
From: Geoff Keating <geoffk at cygnus dot com>
Date: 28 Jun 2000 16:29:15 -0700
CC: gcc at gcc dot gnu dot org
References: <10006272205.ZM13231@mariana.arch.cuhk.edu.hk> <200006280632.IAA01038@loewis.home.cs.tu-berlin.de> <20000628091420.A11370@lucon.org> <200006282030.WAA01169@loewis.home.cs.tu-berlin.de>

"Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de> writes:

> 0804984c R_386_COPY        _16TestInlineStatic.staticVar
> 
> Why is it needed to copy the variable into the program image at run
> time? Couldn't it live in the shared library just fine?

In many ABIs, including ia32, the program can only reference variables
at fixed addresses.  Since shared libraries don't have fixed addresses,
variables are copied at startup time.  Normally, this is OK because
the copied version overrides the one in the shared library, but this
doesn't work if -Bsymbolic is used.
-- 
- Geoffrey Keating <geoffk@cygnus.com>

References:
- linking of inline static methods
  - From: Theodore W. Hall
- Re: linking of inline static methods
  - From: Martin v. Loewis
- Re: linking of inline static methods
  - From: H . J . Lu
- Re: linking of inline static methods
  - From: Martin v. Loewis

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