public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/52297] New: FAIL: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o link, -flto -fgnu-tm Date: Fri, 17 Feb 2012 14:56:00 -0000 [thread overview] Message-ID: <bug-52297-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52297 Bug #: 52297 Summary: FAIL: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o link, -flto -fgnu-tm Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned@gcc.gnu.org ReportedBy: danglin@gcc.gnu.org Host: hppa64-hp-hpux11.11 Target: hppa64-hp-hpux11.11 Build: hppa64-hp-hpux11.11 Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ - flto -fgnu-tm -c -o c_lto_trans-mem-1_0.o /test/gnu/gcc/gcc/gcc/testsuite/gcc. dg/lto/trans-mem-1_0.c (timeout = 300) spawn /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ -flto -fgnu-tm - c -o c_lto_trans-mem-1_0.o /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/lto/trans-mem- 1_0.c PASS: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o assemble, -flto -fgnu-tm Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ - flto -fgnu-tm -c -o c_lto_trans-mem-1_1.o /test/gnu/gcc/gcc/gcc/testsuite/gcc. dg/lto/trans-mem-1_1.c (timeout = 300) spawn /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ -flto -fgnu-tm - c -o c_lto_trans-mem-1_1.o /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/lto/trans-mem-1_1.c PASS: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_1.o assemble, -flto -fgnu-tm Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ c_lto_trans-mem-1_0.o c_lto_trans-mem-1_1.o -flto -fgnu-tm -o gcc-dg-lto-trans-mem-1-01.exe (timeout = 300) spawn /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ c_lto_trans-mem-1_0.o c_lto_trans-mem-1_1.o -flto -fgnu-tm -o gcc-dg-lto-trans-mem-1-01.exe xgcc: error: libitm.spec: No such file or directory compiler exited with status 1 output is: xgcc: error: libitm.spec: No such file or directory FAIL: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o link, -flto -fgnu-tm UNRESOLVED: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o execute -flto -fgnu-tm Similar fails: FAIL: gcc.dg/lto/trans-mem-2 c_lto_trans-mem-2_0.o-c_lto_trans-mem-2_1.o link, -flto -fgnu-tm FAIL: gcc.dg/lto/trans-mem-4 c_lto_trans-mem-4_0.o-c_lto_trans-mem-4_1.o link, -flto -fgnu-tm -bash-3.2$ ./xgcc -B./ -v Reading specs from ./specs COLLECT_GCC=./xgcc COLLECT_LTO_WRAPPER=./lto-wrapper Target: hppa64-hp-hpux11.11 Configured with: ../gcc/configure --with-gnu-as --with-as=/opt/gnu64/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared --with-local-prefix=/opt/gnu64 --prefix=/opt/gnu64/gcc/gcc-4.7 --build=hppa64-hp-hpux11.11 --enable-threads=posix --disable-nls --with-gmp=/opt/gnu64/gcc/gmp --with-libelf=/opt/gnu64 --enable-languages=c,c++,objc,obj-c++,fortran Thread model: posix gcc version 4.7.0 20120216 (experimental) [trunk revision 184311] (GCC)
next reply other threads:[~2012-02-17 14:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-17 14:56 danglin at gcc dot gnu.org [this message] 2012-02-17 16:00 ` [Bug driver/52297] " dominiq at lps dot ens.fr 2012-02-20 12:20 ` [Bug testsuite/52297] [4.7 Regression] " rguenth at gcc dot gnu.org 2012-02-20 13:29 ` dominiq at lps dot ens.fr 2012-02-21 10:16 ` ebotcazou at gcc dot gnu.org 2012-02-22 10:10 ` jakub at gcc dot gnu.org 2012-02-22 20:09 ` aldyh at gcc dot gnu.org 2012-02-22 20:21 ` jakub at gcc dot gnu.org 2012-02-22 21:03 ` aldyh at redhat dot com 2012-02-23 17:58 ` ebotcazou at gcc dot gnu.org 2012-02-29 10:07 ` rguenth at gcc dot gnu.org 2012-02-29 10:13 ` 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-52297-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).