From: Simon Burge <simonb@wasabisystems.com>
To: binutils@sources.redhat.com
Subject: .eh_frame section on alpha
Date: Fri, 24 Dec 2004 13:22:00 -0000 [thread overview]
Message-ID: <20041224132148.GA17654@thoreau.thistledown.com.au> (raw)
Hi folks,
http://sources.redhat.com/ml/binutils/2003-05/msg00863.html added the
generation of a .eh_frame section to all objects that otherwise didn't
have them.
On NetBSD, we have some tight code size constraints for our first stage
boot loader - it needs to fit in 7.5k of space at the start of the disk.
With binutils 2.14, our boot loader was 6880 bytes. With binutils 2.15,
the boot loader is 7848. The only difference in size between the two is
the .eh_frame section:
3 .eh_frame 000003c4 0000000020001990 0000000020001990 00001a40 2**3
CONTENTS, ALLOC, LOAD, READONLY, DATA
What exactly is this section used for? A bit of googling seems to
indicate it's for exception handling, which isn't a C issue.
More importantly, how can I disable the generation of this section? It
seems that only alpha generates an .eh_frame section unconditionally.
Cheers,
Simon.
--
Simon Burge <simonb@wasabisystems.com>
NetBSD Development, Support and Service: http://www.wasabisystems.com/
next reply other threads:[~2004-12-24 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 13:22 Simon Burge [this message]
2004-12-24 15:00 ` Ian Lance Taylor
2004-12-29 7:39 ` Simon Burge
2005-01-04 9:36 ` Nick Clifton
2005-01-04 9:58 ` Jakub Jelinek
2005-01-04 10:06 ` Nick Clifton
2005-01-04 17:51 ` Richard Henderson
2005-01-04 21:27 ` Simon Burge
2005-01-04 22:40 ` Jakub Jelinek
2005-01-05 2:17 ` Simon Burge
2005-01-05 3:14 ` Richard Henderson
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=20041224132148.GA17654@thoreau.thistledown.com.au \
--to=simonb@wasabisystems.com \
--cc=binutils@sources.redhat.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).