From: Geoff Keating <geoffk@ozemail.com.au>
To: ian@zembu.com
Cc: rth@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Trivial patch for elf.sc in ld.
Date: Tue, 28 Sep 1999 21:50:00 -0000 [thread overview]
Message-ID: <199909290437.OAA00961@gluttony.geoffk.wattle.id.au> (raw)
In-Reply-To: <19990929035848.20463.qmail@daffy.airs.com>
> Date: 28 Sep 1999 23:58:48 -0400
> From: Ian Lance Taylor <ian@zembu.com>
> CC: rth@cygnus.com, binutils@sourceware.cygnus.com
>
> Date: Wed, 29 Sep 1999 13:48:05 +1000
> From: Geoff Keating <geoffk@ozemail.com.au>
>
> 1999-09-29 Geoffrey Keating <geoffk@cygnus.com>
>
> * scripttempl/elf.sc (.rel.sdata): Combine all the sdata relocs.
> (.rela.sdata): Likewise.
> (.rel.sbss): Likewise.
> (.rela.sbss): Likewise.
> (.sdata): Don't include .gnu.linkonce.s.* or .sdata.* when
> ld -r.
> (.sbss): Do the same things as for .bss.
>
> Your patch introduces some things you didn't mention in the ChangeLog
> entry: SDATA_START_SYMBOLS and .dynsbss. I don't know why you need
> either of them. .dynsbss in particular sounds odd; does anything
> create that section?
It's created by at least the powerpc linker (which doesn't use this
ldscript), and I expect it needs to be created by every ELF target
with shared libraries and .sdata.
It's needed when you have
extern int foo;
/* do something with foo */
in an application and 'foo' is in a shared library and an 'extern int'
would usually be in the sdata section; you'd normally put such a
symbol in .dynbss.
SDATA_START_SYMBOLS is just there for consistency.
--
Geoffrey Keating <geoffk@cygnus.com>
next prev parent reply other threads:[~1999-09-28 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 4:23 Geoff Keating
1999-09-27 18:24 ` Ian Lance Taylor
1999-09-27 21:30 ` Geoff Keating
1999-09-27 21:42 ` Richard Henderson
1999-09-28 6:26 ` Ian Lance Taylor
1999-09-28 20:49 ` Geoff Keating
1999-09-28 20:59 ` Ian Lance Taylor
1999-09-28 21:50 ` Geoff Keating [this message]
1999-09-28 21:52 ` Ian Lance Taylor
1999-10-06 19:17 ` Geoff Keating
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=199909290437.OAA00961@gluttony.geoffk.wattle.id.au \
--to=geoffk@ozemail.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.com \
--cc=rth@cygnus.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).