public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/61715] New: [4.9/4.10 Regression] binutils trunk ld/LTO 11 test fails when built using GCC 4.9
Date: Fri, 04 Jul 2014 11:53:00 -0000 [thread overview]
Message-ID: <bug-61715-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61715
Bug ID: 61715
Summary: [4.9/4.10 Regression] binutils trunk ld/LTO 11 test
fails when built using GCC 4.9
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
[ filed too: https://sourceware.org/bugzilla/show_bug.cgi?id=17112 ]
on binutils trunk the ld/LTO 11 test fails when built using GCC 4.9, but
succeeds when built using 4.8. seen across all *-linux-gnu architectures.
gcc
-B/scratch/packages/binutils/binutils-2.24.51.20140704/builddir-single/ld/tmpdir/gas/
-I/scratch/packages/binutils/b
inutils-2.24.51.20140704/ld/testsuite/ld-plugin -g -O2 -c -g -O2 -c
/scratch/packages/binutils/binutils-2.24.51.201407
04/ld/testsuite/ld-plugin/dummy.c -o tmpdir/dummy.o
Executing on host: sh -c {gcc
-B/scratch/packages/binutils/binutils-2.24.51.20140704/builddir-single/ld/tmpdir/gas/
-I/s
cratch/packages/binutils/binutils-2.24.51.20140704/ld/testsuite/ld-plugin -g
-O2 -c -g -O2 -c /scratch/packages/binuti
ls/binutils-2.24.51.20140704/ld/testsuite/ld-plugin/dummy.c -o tmpdir/dummy.o
2>&1} /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc
-B/scratch/packages/binutils/binutils-2.24.51.20140704/builddir-single/ld/tmpdir/ld/
-L=/usr/x86_64-linux-gnu/lib64 -
L=/usr/local/lib64 -L=/lib64 -L=/usr/lib64 -L=/usr/x86_64-linux-gnu/lib
-L=/usr/local/lib -L=/lib -L=/usr/lib -o tmpdir
/lto-11.exe
-L/scratch/packages/binutils/binutils-2.24.51.20140704/ld/testsuite/ld-plugin
-O -flto -fuse-linker-plugin tm
pdir/liblto-11.a tmpdir/dummy.o
Executing on host: sh -c {gcc
-B/scratch/packages/binutils/binutils-2.24.51.20140704/builddir-single/ld/tmpdir/ld/
-L=/us
r/x86_64-linux-gnu/lib64 -L=/usr/local/lib64 -L=/lib64 -L=/usr/lib64
-L=/usr/x86_64-linux-gnu/lib -L=/usr/local/lib -L=/l
ib -L=/usr/lib -o tmpdir/lto-11.exe
-L/scratch/packages/binutils/binutils-2.24.51.20140704/ld/testsuite/ld-plugin
-O -f
lto -fuse-linker-plugin tmpdir/liblto-11.a tmpdir/dummy.o 2>&1} /dev/null
ld.tmp (timeout = 300)
spawn [open ...]
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crt1.o: In function
`_start':
/build/glibc-irh9iM/glibc-2.19/csu/../sysdeps/x86_64/start.S:118: undefined
reference to `main'
collect2: error: ld returned 1 exit status
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crt1.o: In function
`_start':
/build/glibc-irh9iM/glibc-2.19/csu/../sysdeps/x86_64/start.S:118: undefined
reference to `main'
collect2: error: ld returned 1 exit status
FAIL: LTO 11
next reply other threads:[~2014-07-04 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 11:53 doko at gcc dot gnu.org [this message]
2014-07-05 6:39 ` [Bug lto/61715] " trippels 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-61715-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: 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).