From: "Mark E." <snowball@snowball.frogspace.net>
To: binutils@sourceware.cygnus.com
Subject: update for djgpp linker script
Date: Fri, 20 Aug 1999 17:02:00 -0000 [thread overview]
Message-ID: <E11HyNx-0006E3-00@digitalspace.frogspace.net> (raw)
Hello,
It turns out that the ___EH* symbols aren't needed. The LONG(0) after
.eh_fram* is needed for compatibility with the DJGPP version of gcc
2.8.1, so it will have to stay for now.
Also note that .?tors. is hardcoded into gcc 2.95, so there is no choice
on this.
ld/Changelog:
1999-08-19 Mark Elbrecht <snowball3@bigfoot.com>
* scripttempl/i386go32.sc (___EH_FRAME_BEGIN__,
___EH_FRAME_END__): Delete.
(_etext, _end): Move the semicolon inside the brace.
* scripttempl/i386go32.sc: Support the g++ attribute 'init_priority'.
Add a period to link once section names.
*** scripttempl/i386go32.sc.orig Mon Aug 9 23:07:46 1999
--- scripttempl/i386go32.sc Fri Aug 20 19:51:34 1999
*************** EXE=${CONSTRUCTING+${RELOCATING+-exe}}
*** 5,12 ****
# These are substituted in as variables in order to get '}' in a shell
# conditional expansion.
! CTOR='.ctor : { *(.ctor) }'
! DTOR='.dtor : { *(.dtor) }'
cat <<EOF
OUTPUT_FORMAT("${OUTPUT_FORMAT}${EXE}")
--- 5,14 ----
# These are substituted in as variables in order to get '}' in a shell
# conditional expansion.
! # Support the g++ attribute 'init_priority' from GCC 2.95 and above
! # by sorting sections starting with '.ctors.' and '.dtors.'
! CTOR='.ctor : { (*(SORT(.ctors.*))) *(.ctor) }'
! DTOR='.dtor : { (*(SORT(.dtors.*))) *(.dtor) }'
cat <<EOF
OUTPUT_FORMAT("${OUTPUT_FORMAT}${EXE}")
*************** SECTIONS
*** 26,46 ****
}
.data ${RELOCATING+ ${DATA_ALIGNMENT}} : {
${RELOCATING+djgpp_first_ctor = . ;
*(.ctor)
djgpp_last_ctor = . ;}
${RELOCATING+djgpp_first_dtor = . ;
*(.dtor)
djgpp_last_dtor = . ;}
*(.data)
${RELOCATING+*(.gcc_exc*)}
- ${RELOCATING+___EH_FRAME_BEGIN__ = . ;}
${RELOCATING+*(.eh_fram*)}
- ${RELOCATING+___EH_FRAME_END__ = . ;}
${RELOCATING+LONG(0);}
${RELOCATING+*(.gnu.linkonce.d*)}
! ${RELOCATING+edata = . ; _edata = .};
${RELOCATING+. = ALIGN(${SEGMENT_SIZE});}
}
${CONSTRUCTING+${RELOCATING-$CTOR}}
--- 28,48 ----
}
.data ${RELOCATING+ ${DATA_ALIGNMENT}} : {
${RELOCATING+djgpp_first_ctor = . ;
+ (*(SORT(.ctors.*)))
*(.ctor)
djgpp_last_ctor = . ;}
${RELOCATING+djgpp_first_dtor = . ;
+ (*(SORT(.dtors.*)))
*(.dtor)
djgpp_last_dtor = . ;}
*(.data)
${RELOCATING+*(.gcc_exc*)}
${RELOCATING+*(.eh_fram*)}
${RELOCATING+LONG(0);}
${RELOCATING+*(.gnu.linkonce.d*)}
! ${RELOCATING+edata = . ; _edata = . ;}
${RELOCATING+. = ALIGN(${SEGMENT_SIZE});}
}
${CONSTRUCTING+${RELOCATING-$CTOR}}
*************** SECTIONS
*** 49,55 ****
{
*(.bss)
*(COMMON)
! ${RELOCATING+ end = . ; _end = .};
${RELOCATING+ . = ALIGN(${SEGMENT_SIZE});}
}
}
--- 51,57 ----
{
*(.bss)
*(COMMON)
! ${RELOCATING+ end = . ; _end = . ;}
${RELOCATING+ . = ALIGN(${SEGMENT_SIZE});}
}
}
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
next reply other threads:[~1999-08-20 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-20 17:02 Mark E. [this message]
1999-08-24 20:13 Mark E.
1999-08-24 20:13 Mark E.
1999-08-24 20:13 Mark E.
1999-08-24 20:13 Mark E.
1999-08-24 20:18 Mark E.
1999-08-24 20:18 Mark E.
1999-08-24 20:20 Mark E.
1999-08-24 20:20 Mark E.
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=E11HyNx-0006E3-00@digitalspace.frogspace.net \
--to=snowball@snowball.frogspace.net \
--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).