public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/63409] New: [5 Regression] FAIL: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o link, -flto -O2 -Wno-odr -fno-linker-plugin Date: Mon, 29 Sep 2014 15:58:00 -0000 [thread overview] Message-ID: <bug-63409-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63409 Bug ID: 63409 Summary: [5 Regression] FAIL: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o link, -flto -O2 -Wno-odr -fno-linker-plugin Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: ubizjak at gmail dot com This can be triggered on Fedora20 with: make check-c++ RUNTESTFLAGS="--target_board=unix/-fno-use-linker-plugin lto.exp=pr63270_?.C" spawn -ignore SIGHUP /ssd/uros/gcc-build/gcc/testsuite/g++/../../xg++ -B/ssd/uros/gcc-build/gcc/testsuite/g++/../../ cp_lto_pr63270_0.o cp_lto_pr63270_1.o -fno-diagnostics-show-caret -fdiagnostics-color=never -nostdinc++ -I/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/uros/gcc-svn/trunk/libstdc++-v3/libsupc++ -I/home/uros/gcc-svn/trunk/libstdc++-v3/include/backward -I/home/uros/gcc-svn/trunk/libstdc++-v3/testsuite/util -fmessage-length=0 -flto -O2 -Wno-odr -L/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/./libstdc++-v3/src/.libs -B/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/./libstdc++-v3/src/.libs -L/ssd/uros/gcc-build/x86_64-unknown-linux-gnu/./libstdc++-v3/src/.libs -fno-use-linker-plugin -o g++-dg-lto-pr63270-01.exe cp_lto_pr63270_0.o: In function `v8::internal::fn1()': pr63270_0.C:(.text+0xa): undefined reference to `v8::internal::B::B(int)' pr63270_0.C:(.text+0x16): undefined reference to `v8::internal::B::B(int)' pr63270_0.C:(.text+0x22): undefined reference to `v8::internal::A::A(int)' pr63270_0.C:(.text+0x27): undefined reference to `v8::internal::G::m_fn1()' collect2: error: ld returned 1 exit status compiler exited with status 1 output is: cp_lto_pr63270_0.o: In function `v8::internal::fn1()': pr63270_0.C:(.text+0xa): undefined reference to `v8::internal::B::B(int)' pr63270_0.C:(.text+0x16): undefined reference to `v8::internal::B::B(int)' pr63270_0.C:(.text+0x22): undefined reference to `v8::internal::A::A(int)' pr63270_0.C:(.text+0x27): undefined reference to `v8::internal::G::m_fn1()' collect2: error: ld returned 1 exit status FAIL: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o link, -flto -O2 -Wno-odr UNRESOLVED: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o execute -flto -O2 -Wno-odr
next reply other threads:[~2014-09-29 15:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-29 15:58 ubizjak at gmail dot com [this message] 2014-09-30 10:18 ` [Bug lto/63409] " rguenth at gcc dot gnu.org 2014-09-30 10:46 ` dominiq at lps dot ens.fr 2014-09-30 11:10 ` mliska at suse dot cz 2014-10-03 13:33 ` ubizjak at gmail dot com 2014-10-06 14:33 ` ro at gcc dot gnu.org 2014-10-06 16:18 ` mliska at suse dot cz 2014-10-07 6:45 ` ubizjak at gmail dot com 2014-10-07 8:28 ` mliska at suse dot cz 2014-10-07 11:01 ` rguenth 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-63409-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).