public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/65718] New: g++.dg/lto/pr65276 FAILs Date: Thu, 09 Apr 2015 15:25:00 -0000 [thread overview] Message-ID: <bug-65718-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65718 Bug ID: 65718 Summary: g++.dg/lto/pr65276 FAILs Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: aldyh at gcc dot gnu.org Host: i386-pc-solaris2.11, sparc-sun-solaris2.11 Target: i386-pc-solaris2.11, sparc-sun-solaris2.11 Build: i386-pc-solaris2.11, sparc-sun-solaris2.11 The new g++.dg/lto/pr65276 FAILs on Solaris 11 when using Sun ld: UNRESOLVED: g++.dg/lto/pr65276 cp_lto_pr65276_0.o-cp_lto_pr65276_1.o execute -flto -O0 -std=c++11 FAIL: g++.dg/lto/pr65276 cp_lto_pr65276_0.o-cp_lto_pr65276_1.o link, -flto -O0 -std=c++11 The failure is 32-bit only, the 64-bit multilib is fine. The log only contains truncated linker output: output is: ld: warning: symbol 'vtable for std::runtime_error' has differing sizes:^M (file cp_lto_pr65276_1.o value=0x10; file /var/gcc/regression/trunk/11-gcc/build/i386-pc-solaris2.11/. Re-running the test manually gives the full output: ld: warning: symbol 'vtable for std::runtime_error' has differing sizes: (file cp_lto_pr65276_1.o value=0x10; file /var/gcc/regression/trunk/11-gcc/build/i386-pc-solaris2.11/./libstdc++-v3/src/.libs/libstdc++.so value=0x14); cp_lto_pr65276_1.o definition taken ld: warning: symbol 'vtable for std::exception' has differing sizes: (file cp_lto_pr65276_1.o value=0x10; file /var/gcc/regression/trunk/11-gcc/build/i386-pc-solaris2.11/./libstdc++-v3/src/.libs/libstdc++.so value=0x14); cp_lto_pr65276_1.o definition taken ld: warning: symbol '_ZTVSt13runtime_error' has differing sizes: (file /var/tmp//ccUIayls.ltrans0.ltrans.o value=0x10; file /var/gcc/regression/trunk/11-gcc/build/i386-pc-solaris2.11/./libstdc++-v3/src/.libs/libstdc++.so value=0x14); /var/tmp//ccUIayls.ltrans0.ltrans.o definition taken ld: warning: symbol '_ZTVSt9exception' has differing sizes: (file /var/tmp//ccUIayls.ltrans0.ltrans.o value=0x10; file /var/gcc/regression/trunk/11-gcc/build/i386-pc-solaris2.11/./libstdc++-v3/src/.libs/libstdc++.so value=0x14); /var/tmp//ccUIayls.ltrans0.ltrans.o definition taken Rainer
next reply other threads:[~2015-04-09 15:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-09 15:25 ro at gcc dot gnu.org [this message] 2015-04-09 15:25 ` [Bug lto/65718] " ro at gcc dot gnu.org 2015-04-10 7:42 ` [Bug testsuite/65718] [5 Regression] " rguenth at gcc dot gnu.org 2015-04-22 11:58 ` [Bug testsuite/65718] [5/6 " jakub 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-65718-4@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: linkBe 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).