From: Geoff Keating <geoffk@ozemail.com.au>
To: rth@cygnus.com, binutils@sourceware.cygnus.com
Subject: Trivial patch for elf.sc in ld.
Date: Mon, 27 Sep 1999 04:23:00 -0000 [thread overview]
Message-ID: <199909271111.VAA01659@gluttony.geoffk.wattle.id.au> (raw)
I think this is really self-explanatory. OK to commit?
--
Geoffrey Keating <geoffk@cygnus.com>
===File ~/patches/cygnus/tx49-bin-slinkonce.patch===========
md5sum: 01c7f288ab65b2dc 1f8b47196257f7c3 348219
Index: binutils/ld/ChangeLog
0a
Wed Sep 22 12:42:36 1999 Geoffrey Keating <geoffk@cygnus.com>
* scripttempl/elf.sc (.sdata): Include .gnu.linkonce.s.* sections
in .sdata too.
.
Changed files:
binutils/ld/ChangeLog
binutils/ld/scripttempl/elf.sc
md5sum: 86ddf7df91f7b761 c5d23ef89c14ef71 10785
--- /sloth/disk0/co/binutils-mainline/binutils/ld/scripttempl/elf.sc Mon Sep 27 18:29:33 1999
+++ binutils/ld/scripttempl/elf.sc Mon Sep 27 19:45:02 1999
@@ -232,7 +232,7 @@ cat <<EOF
/* We want the small data sections together, so single-instruction offsets
can access them all, and initialized data all before uninitialized, so
we can shorten the on-disk segment size. */
- .sdata ${RELOCATING-0} : { *(.sdata) *(.sdata.*) }
+ .sdata ${RELOCATING-0} : { *(.sdata) *(.sdata.*) *(.gnu.linkonce.s.*) }
${RELOCATING+${OTHER_GOT_SECTIONS}}
${RELOCATING+_edata = .;}
${RELOCATING+PROVIDE (edata = .);}
============================================================
next reply other threads:[~1999-09-27 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 4:23 Geoff Keating [this message]
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
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=199909271111.VAA01659@gluttony.geoffk.wattle.id.au \
--to=geoffk@ozemail.com.au \
--cc=binutils@sourceware.cygnus.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).