public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46055] [4.6 Regression] -fwhopr failed configure test
Date: Mon, 18 Oct 2010 12:24:00 -0000	[thread overview]
Message-ID: <20101018122400.ehvwb1vt3QEPy3F9x0B7MFgCUoQAl8YBjMVtQ1xFNoo@z> (raw)
In-Reply-To: <bug-46055-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46055

--- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> 2010-10-18 12:23:36 UTC ---
(In reply to comment #8)
> Hmm, does -fuse-linker-plugin have the same side-effects as -fwhole-program?
> That will break symbol use by dlopened objects and we have to avoid that.
> 

[hjl@gnu-6 pr46055]$ make
/export/build/gnu/gcc/build-x86_64-linux/prev-gcc/xgcc
-B/export/build/gnu/gcc/build-x86_64-linux/prev-gcc/ -O2 -fuse-linker-plugin
-fwhopr -o foo foo.i
ld.gold: /tmp/ccIRVeGM.ltrans0.ltrans.o: in function
main:ccIRVeGM.ltrans0.o(.text+0x3): error: undefined reference to
'pstat_getstatic'
collect2: ld returned 1 exit status
make: *** [foo] Error 1
[hjl@gnu-6 pr46055]$ /export/build/gnu/gcc/build-x86_64-linux/prev-gcc/xgcc
-B/export/build/gnu/gcc/build-x86_64-linux/prev-gcc/ -O2 -fwhopr -o foo foo.i
/tmp/cczPtxXa.o: In function `main':
foo.i:(.text+0x3): undefined reference to `pstat_getstatic'
collect2: ld returned 1 exit status
[hjl@gnu-6 pr46055]$ /export/build/gnu/gcc/build-x86_64-linux/prev-gcc/xgcc
-B/export/build/gnu/gcc/build-x86_64-linux/prev-gcc/ -O2 -fwhole-program -o foo
foo.i
/tmp/ccB81NJo.o: In function `main':
foo.i:(.text+0x3): undefined reference to `pstat_getstatic'
collect2: ld returned 1 exit status
[hjl@gnu-6 pr46055]$ /export/build/gnu/gcc/build-x86_64-linux/prev-gcc/xgcc
-B/export/build/gnu/gcc/build-x86_64-linux/prev-gcc/ -O2 -fwhole-program -o foo
foo.i -fuse-linker-plugin
ld.gold: /tmp/cc4NeRs5.o: in function main:foo.i(.text+0x3): error: undefined
reference to 'pstat_getstatic'
collect2: ld returned 1 exit status
[hjl@gnu-6 pr46055]$ 

It only happens with "-fuse-linker-plugin -fwhopr".


  parent reply	other threads:[~2010-10-18 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17  7:51 [Bug lto/46055] New: [4.6 Regression] LTO failed to bootstrap hjl.tools at gmail dot com
2010-10-17  7:54 ` [Bug lto/46055] " hjl.tools at gmail dot com
2010-10-17 20:55 ` hjl.tools at gmail dot com
2010-10-17 21:22 ` [Bug lto/46055] [4.6 Regression] -fwhopr failed LTO bootstrap test hjl.tools at gmail dot com
2010-10-17 21:33 ` [Bug bootstrap/46055] [4.6 Regression] -fwhopr failed configure test hjl.tools at gmail dot com
2010-10-17 22:17 ` hjl.tools at gmail dot com
2010-10-17 22:28 ` andi-gcc at firstfloor dot org
2010-10-18  9:55 ` rguenth at gcc dot gnu.org
2010-10-18  9:58 ` rguenth at gcc dot gnu.org
2010-10-18 12:24 ` hjl.tools at gmail dot com [this message]
2010-10-18 15:12 ` hubicka at ucw dot cz
2010-10-18 15:47 ` hubicka at ucw dot cz
2010-10-20 21:17 ` hjl.tools at gmail dot com

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=20101018122400.ehvwb1vt3QEPy3F9x0B7MFgCUoQAl8YBjMVtQ1xFNoo@z \
    --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).