public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Mark P. Mitchell" <mark@codesourcery.com>
To: binutils@sourceware.cygnus.com
Subject: PATCH for IRIX6/linkonce sections
Date: Sun, 18 Jul 1999 22:03:00 -0000	[thread overview]
Message-ID: <199907190503.XAA1671749@nirvana.acl.lanl.gov> (raw)

In order to get linkonce sections working on IRIX6, we need something like
the following patch.  It's ugly to put this is elf.sc, but putting
it in elf32bmipn32.sh didn't work because RELOCATING is not defined
at the point that file is sourced.  (Another approach would be to change
that, but that change would be obtrusive, and could subtly affect other
emulations.)

OK to check in?

--

Sun Jul 18 23:00:52 1999  Mark P. Mitchell  <mark@codesourcery.com>

	* scripttempl/elf.sc: Handle .MIPS.events and .MIPS.content sections
	in conjunction with linkonce sections.

Index: scripttempl/elf.sc
===================================================================
RCS file: /cvs/binutils/binutils/ld/scripttempl/elf.sc,v
retrieving revision 1.3
diff -c -p -r1.3 elf.sc
*** elf.sc	1999/07/14 16:45:54	1.3
--- elf.sc	1999/07/19 05:00:33
*************** SECTIONS
*** 279,284 ****
--- 279,322 ----
    .debug_typenames 0 : { *(.debug_typenames) }
    .debug_varnames  0 : { *(.debug_varnames) }
  
+   /* SGI extensions.  */
+   .MIPS.events.text ${RELOCATING-0} : 
+     {
+        *(.MIPS.events.text)
+        *(.MIPS.events.text.*)
+        ${RELOCATING+*(.MIPS.events.gnu.linkonce.t*)}
+     }
+   .MIPS.content.text ${RELOCATING-0} : 
+     {
+        *(.MIPS.content.text)
+        *(.MIPS.content.text*)
+        ${RELOCATING+*(.MIPS.content.gnu.linkonce.t*)}
+     }
+   .MIPS.events.data ${RELOCATING-0} : 
+     {
+        *(.MIPS.events.data)
+        *(.MIPS.events.data.*)
+        ${RELOCATING+*(.MIPS.events.gnu.linkonce.d*)}
+     }
+   .MIPS.content.data ${RELOCATING-0} : 
+     {
+        *(.MIPS.content.data)
+        *(.MIPS.content.data*)
+        ${RELOCATING+*(.MIPS.content.gnu.linkonce.d*)}
+     }
+   .MIPS.events.rodata ${RELOCATING-0} : 
+     {
+        *(.MIPS.events.rodata)
+        *(.MIPS.events.rodata.*)
+        ${RELOCATING+*(.MIPS.events.gnu.linkonce.r*)}
+     }
+   .MIPS.content.rodata ${RELOCATING-0} : 
+     {
+        *(.MIPS.content.rodata)
+        *(.MIPS.content.rodata*)
+        ${RELOCATING+*(.MIPS.content.gnu.linkonce.r*)}
+     }
+ 
    ${RELOCATING+${OTHER_RELOCATING_SECTIONS}}
  
    /* These must appear regardless of ${RELOCATING}.  */

             reply	other threads:[~1999-07-18 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-18 22:03 Mark P. Mitchell [this message]
1999-07-19  9:37 ` Ian Lance Taylor
1999-07-19  9:45   ` Mark Mitchell
1999-07-19 12:14     ` Ian Lance Taylor
1999-07-19 12:30       ` Mark Mitchell

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=199907190503.XAA1671749@nirvana.acl.lanl.gov \
    --to=mark@codesourcery.com \
    --cc=binutils@sourceware.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).