From: Richard Henderson <rth@redhat.com>
To: yunfeng zhang <zyf.zeroos@gmail.com>
Cc: gcc@gcc.gnu.org, Andrew Haley <aph@redhat.com>
Subject: Re: No .got section in ELF
Date: Thu, 26 Nov 2009 03:11:00 -0000 [thread overview]
Message-ID: <4B0DF1EC.30001@redhat.com> (raw)
In-Reply-To: <4df04b840911251824j71fa1d33i2cecc9481617dda5@mail.gmail.com>
On 11/25/2009 06:24 PM, yunfeng zhang wrote:
> It seems that original limitation isn't clear or sufficient
>
> For a sample:
>
> // f.c
> int g;
> void foo(void)
> {
> g = 1;
> }
>
> compile with `gcc -shared -fPIC -Wl,-soname,f.so,-Map,f.map -o f.so f.c'...
With -fPIC, the variable G may be overridden by another variable of the
same name from another shared object earlier in the search path. That
is, the offset is *not* fixed because the final address of G may reside
in a different .so file.
Change your program to
static int g;
or
extern int g __attribute__((visibility("hidden")));
int g;
and compare the results. In either case G is known to resolve to the
instance present in f.so. In either case we'll use a constant offset.
You really need to understand how ELF actually works before suggesting
that it's broken.
r~
next prev parent reply other threads:[~2009-11-26 3:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 1:58 yunfeng zhang
2009-11-24 10:00 ` Andrew Haley
2009-11-24 17:10 ` Richard Henderson
2009-11-26 2:24 ` yunfeng zhang
2009-11-26 3:11 ` Richard Henderson [this message]
2009-11-26 6:04 ` yunfeng zhang
2009-11-26 7:55 ` Alexandre Oliva
2009-11-27 2:18 ` yunfeng zhang
2009-11-27 4:12 ` Dave Korn
2009-11-27 4:43 ` yunfeng zhang
2009-11-27 4:46 ` Dave Korn
2009-11-27 13:35 ` Alexandre Oliva
2009-11-30 11:10 ` Yunfeng ZHANG
2009-11-27 4:58 ` Jie Zhang
2009-11-27 6:42 ` yunfeng zhang
2009-11-27 14:16 ` Ian Lance Taylor
2009-11-27 4:51 Dmitry Gorbachev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0DF1EC.30001@redhat.com \
--to=rth@redhat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=zyf.zeroos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).