public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vhaisman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/56088] [4.8 Regression] LTO error: error: inlining failed in call to always_inline ‘vswprintf’: recursive inlining
Date: Mon, 28 Jan 2013 20:13:00 -0000	[thread overview]
Message-ID: <bug-56088-4-rKzEnzHJ9Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56088-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Václav Zeman <vhaisman at gmail dot com> 2013-01-28 20:12:49 UTC ---
(In reply to comment #7)
> What linker are you using?  It seems to work for me with GNU ld 2.23.1.
> 
> Using
> 
> > ./xg++ -B. t2.ii -r -nostdlib -flto -std=c++11 -march=amdfam10 -mfxsr -fPIC -O3 -flto-partition=none -fuse-linker-plugin
> 
> and preprocessed source.  Did you use the same flags compiling timehelper.o?
I am seeing this when I add -Wl,-v to command line:

/usr/bin/ld.gold -plugin
/home/wilx/gcc48/libexec/gcc/x86_64-linux-gnu/4.8.0/liblto_plugin.so
-plugin-opt=/home/wilx/gcc48/libexec/gcc/x86_64-linux-gnu/4.8.0/lto-wrapper
-plugin-opt=-fresolution=/tmp/cchgMTW0.res --sysroot=/ --eh-frame-hdr -m
elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o out.so -r
-L/home/wilx/gcc48/lib/gcc/x86_64-linux-gnu/4.8.0
-L/home/wilx/gcc48/lib/gcc/x86_64-linux-gnu/4.8.0/../../../../lib64
-L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu
-L/usr/lib/../lib64 -L/home/wilx/gcc48/lib/gcc/x86_64-linux-gnu/4.8.0/../../..
-v ./timehelper.o
GNU gold (GNU Binutils for Ubuntu 2.22.90.20120924) 1.11 g++-4.8
@/tmp/cc2L4QqZ.args


  parent reply	other threads:[~2013-01-28 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 20:44 [Bug c++/56088] New: " vhaisman at gmail dot com
2013-01-23 20:45 ` [Bug c++/56088] " vhaisman at gmail dot com
2013-01-23 20:47 ` vhaisman at gmail dot com
2013-01-23 20:49 ` [Bug lto/56088] " pinskia at gcc dot gnu.org
2013-01-23 20:50 ` pinskia at gcc dot gnu.org
2013-01-23 20:54 ` vhaisman at gmail dot com
2013-01-23 22:20 ` vhaisman at gmail dot com
2013-01-23 22:28 ` pinskia at gcc dot gnu.org
2013-01-24 12:13 ` [Bug lto/56088] [4.8 Regression] " rguenth at gcc dot gnu.org
2013-01-28 14:31 ` rguenth at gcc dot gnu.org
2013-01-28 20:13 ` vhaisman at gmail dot com [this message]
2013-03-22 14:46 ` [Bug lto/56088] [4.8/4.9 " jakub at gcc dot gnu.org
2014-02-16  6:25 ` yshuiv7 at gmail dot com
2014-02-16  6:34 ` vhaisman at gmail dot com
2014-02-16  8:16 ` trippels at gcc dot gnu.org
2014-02-16  8:25 ` 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-56088-4-rKzEnzHJ9Y@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).