public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57038] Latest libreoffice compilation fails with enabled LTO
Date: Wed, 22 May 2013 11:36:00 -0000 [thread overview]
Message-ID: <bug-57038-4-RQ6sMA6SJF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57038-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57038
--- Comment #24 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
S=/home/marxin/libreoffice && O=$S/solver/unxlngx6.pro &&
W=$S/workdir/unxlngx6.pro && mkdir -p $W/LinkTarget/Executable/ && g++ -flto
-fno-fat-lto-objects -fuse-linker-plugin -O2 -Wl,-z,origin
'-Wl,-rpath,$ORIGIN/../lib:$ORIGIN' -Wl,-rpath-link,$O/lib -Wl,-z,defs
-Wl,-rpath-link,/lib:/usr/lib -Wl,-z,combreloc -L$O/lib -Wl,--hash-style=gnu
-Wl,--dynamic-list-cpp-new -Wl,--dynamic-list-cpp-typeinfo
-Wl,-Bsymbolic-functions -Wl,-O1 -Wl,-S
$W/CxxObject/i18npool/source/localedata/LocaleNode.o
$W/CxxObject/i18npool/source/localedata/filewriter.o
$W/CxxObject/i18npool/source/localedata/saxparser.o -Wl,--start-group
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal
-o $W/LinkTarget/Executable/saxparser
/home/marxin/libreoffice/workdir/unxlngx6.pro/CxxObject/i18npool/source/localedata/saxparser.o
(symbol from plugin): undefined reference to `typeinfo for
com::sun::star::uno::Exception'
/home/marxin/libreoffice/workdir/unxlngx6.pro/CxxObject/i18npool/source/localedata/saxparser.o
(symbol from plugin): undefined reference to `typeinfo name for
com::sun::star::uno::RuntimeException'
/home/marxin/libreoffice/workdir/unxlngx6.pro/CxxObject/i18npool/source/localedata/saxparser.o
(symbol from plugin): undefined reference to `typeinfo for
com::sun::star::uno::RuntimeException'
/home/marxin/libreoffice/workdir/unxlngx6.pro/CxxObject/i18npool/source/localedata/saxparser.o
(symbol from plugin): undefined reference to `typeinfo name for
com::sun::star::uno::Exception'
actually this sounds more like a GCC bug, still. We should not optimize out
typeinfos.
Can you please relink with -Wl,--no-demangle --save-temps -fdump-ipa-cgraph (so
we now unmangled typeinfo symbol name) and send the resolution file +
*wpa*cgraph file?
Honza
next prev parent reply other threads:[~2013-05-22 11:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 21:08 [Bug c++/57038] New: " marxin.liska at gmail dot com
2013-04-24 13:35 ` [Bug c++/57038] " hubicka at gcc dot gnu.org
2013-04-26 9:24 ` marxin.liska at gmail dot com
2013-05-03 11:20 ` marxin.liska at gmail dot com
2013-05-03 12:15 ` hubicka at ucw dot cz
2013-05-03 12:44 ` marxin.liska at gmail dot com
2013-05-03 13:03 ` hubicka at ucw dot cz
2013-05-03 13:08 ` marxin.liska at gmail dot com
2013-05-03 15:19 ` marxin.liska at gmail dot com
2013-05-03 16:48 ` hubicka at ucw dot cz
2013-05-03 16:59 ` marxin.liska at gmail dot com
2013-05-03 17:00 ` marxin.liska at gmail dot com
2013-05-13 12:08 ` hubicka at gcc dot gnu.org
2013-05-13 13:42 ` marxin.liska at gmail dot com
2013-05-13 17:18 ` hubicka at ucw dot cz
2013-05-13 18:49 ` hubicka at gcc dot gnu.org
2013-05-13 19:45 ` marxin.liska at gmail dot com
2013-05-20 19:16 ` marxin.liska at gmail dot com
2013-05-22 11:36 ` hubicka at gcc dot gnu.org [this message]
2013-05-22 14:40 ` hubicka at gcc dot gnu.org
2013-06-21 9:02 ` marxin.liska at gmail dot com
2013-06-21 12:53 ` hubicka at gcc dot gnu.org
2013-06-22 20:57 ` hubicka at ucw dot cz
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-57038-4-RQ6sMA6SJF@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).