public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stefan Bylund <steby@enea.se>
To: gcc-help@gcc.gnu.org
Subject: Why eh_frame sections in libgcc.a?
Date: Thu, 10 Oct 2002 06:13:00 -0000	[thread overview]
Message-ID: <3DA57D58.4468FCC3@enea.se> (raw)

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

When building GCC 3.2 for powerpc-eabi, ".eh_frame" exception handling sections
are generated in libgcc.a for the following objects:

_divdi3.o
_moddi3.o
_udivdi3.o
_umoddi3.o
_udiv_w_sdiv.o
_udivmoddi4.o
unwind-dw2.o
unwind-dw2-fde.o

I can understand why such sections are generated for unwind-dw2.o and
unwind-dw2-fde.o which are used by libstdc++.a and libsupc++.a but why are they
generated for the other integer division related objects? Is there support for
throwing C++ exceptions when dividing by zero? What happens with such support in
a plain C application? Are these ".eh_frame" sections in libgcc.a unused and
harmless when compiling a plain C application and linking it with libgcc.a?

/Stefan


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Card for Stefan Bylund --]
[-- Type: text/x-vcard; charset=us-ascii; name="steby.vcf", Size: 275 bytes --]

begin:vcard 
n:Bylund;Stefan
tel;cell:+46 709 714 325
tel;work:+46 8 507 143 25
x-mozilla-html:FALSE
url:http://www.ose.com
org:OSE Systems
adr:;;Nytorpsvägen 5;Täby;;183 23;Sweden
version:2.1
email;internet:steby@enea.se
title:Software Engineer
fn:Stefan Bylund
end:vcard

                 reply	other threads:[~2002-10-10 13:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3DA57D58.4468FCC3@enea.se \
    --to=steby@enea.se \
    --cc=gcc-help@gcc.gnu.org \
    /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).