public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56840] a.out aborts instead of catching exception with -flto and -static-libstdc++
Date: Thu, 04 Apr 2013 14:39:00 -0000 [thread overview]
Message-ID: <bug-56840-4-KHNGNPDVZV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56840-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56840
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-04-04
CC| |iant at google dot com
Host|CentOS release 6.4 (Final) |
|x86_64 GNU/Linux |
Ever Confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> 2013-04-04 14:39:30 UTC ---
Confirmed with using gold, works when using GNU ld (2.23.1). This is probably
a linker issue then.
Ian?
gold:
1
t.o 16
165 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZN4MyExD2Ev
185 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZTV4MyEx
237 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZN4MyExD1Ev
246 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZN4MyExD0Ev
255 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZN4MyExC2Ev
261 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZN4MyExC1Ev
266 46dc27f64f5c9b0d PREVAILING_DEF main
209 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZTI4MyEx
232 46dc27f64f5c9b0d PREVAILING_DEF_IRONLY _ZTS4MyEx
269 46dc27f64f5c9b0d RESOLVED_EXEC __gxx_personality_v0
220 46dc27f64f5c9b0d RESOLVED_EXEC _ZTVN10__cxxabiv117__class_type_infoE
276 46dc27f64f5c9b0d RESOLVED_EXEC _ZdlPv
283 46dc27f64f5c9b0d RESOLVED_EXEC __cxa_end_catch
287 46dc27f64f5c9b0d RESOLVED_EXEC __cxa_begin_catch
293 46dc27f64f5c9b0d RESOLVED_EXEC __cxa_throw
301 46dc27f64f5c9b0d RESOLVED_EXEC __cxa_allocate_exception
bfd:
1
t.o 16
165 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZN4MyExD2Ev
185 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZTV4MyEx
237 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZN4MyExD1Ev
246 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZN4MyExD0Ev
255 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZN4MyExC2Ev
261 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZN4MyExC1Ev
266 4ce296565b57ee97 PREVAILING_DEF main
209 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZTI4MyEx
232 4ce296565b57ee97 PREVAILING_DEF_IRONLY _ZTS4MyEx
269 4ce296565b57ee97 RESOLVED_EXEC __gxx_personality_v0
220 4ce296565b57ee97 RESOLVED_EXEC _ZTVN10__cxxabiv117__class_type_infoE
276 4ce296565b57ee97 RESOLVED_EXEC _ZdlPv
283 4ce296565b57ee97 RESOLVED_EXEC __cxa_end_catch
287 4ce296565b57ee97 RESOLVED_EXEC __cxa_begin_catch
293 4ce296565b57ee97 RESOLVED_EXEC __cxa_throw
301 4ce296565b57ee97 RESOLVED_EXEC __cxa_allocate_exception
so we probably produce the same LTRANS units for the same link.
next prev parent reply other threads:[~2013-04-04 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 14:22 [Bug c++/56840] New: " wem@trash-mail.com
2013-04-04 14:36 ` [Bug c++/56840] " wem@trash-mail.com
2013-04-04 14:39 ` rguenth at gcc dot gnu.org [this message]
2013-04-04 16:52 ` [Bug lto/56840] " ian at airs dot com
2022-08-01 17:36 ` redi at gcc dot gnu.org
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=bug-56840-4-KHNGNPDVZV@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).