public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53282] lto and visibility-inlines-hidden makes "wrongly" hidden symbols and in a way that depends on the order of the input compilation units
Date: Wed, 09 May 2012 12:46:00 -0000 [thread overview]
Message-ID: <bug-53282-4-DwEL7YYlzL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53282-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282
--- Comment #13 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-05-09 12:35:51 UTC ---
On 9 May, 2012, at 2:21 PM, hubicka at ucw dot cz wrote:
> No, LTO plugin is needed for "proper" LTO and will always be. We have
> alternative
> non-plugin path that results in poorer code quality.
I see.
could you please specify the configure options to be used ?
I tried
--enable-linker-plugin
and does not help
thois is how I configured latest version of the trunk
c++ -v
Using built-in specs.
COLLECT_GCC=c++
COLLECT_LTO_WRAPPER=/afs/cern.ch/user/i/innocent/w2/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ./configure --prefix=/afs/cern.ch/user/i/innocent/w2
--enable-languages=c,c++,fortran -enable-gold=yes --enable-lto
--with-build-config=bootstrap-lto --with-gmp-lib=/usr/local/lib64
--with-mpfr-lib=/usr/local/lib64 -with-mpc-lib=/usr/local/lib64
--enable-cloog-backend=isl --with-cloog=/usr/local
--with-ppl-lib=/usr/local/lib64 CFLAGS='-O2 -ftree-vectorize -fPIC'
CXXFLAGS='-O2 -fPIC -ftree-vectorize -fvisibility-inlines-hidden -march=native'
-enable-libitm -disable-multilib --enable-linker-plugin
Thread model: posix
gcc version 4.8.0 20120509 (experimental) [trunk revision 187326] (GCC)
and I get
c++ -fuse-linker-plugin -fvisibility-inlines-hidden -O2 -flto -shared -fPIC -o
bha.so d1.cc d2.cc d3.cc
c++: error: -fuse-linker-plugin is not supported in this configuration
next prev parent reply other threads:[~2012-05-09 12:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:51 [Bug lto/53282] New: " vincenzo.innocente at cern dot ch
2012-05-08 13:57 ` [Bug lto/53282] " rguenth at gcc dot gnu.org
2012-05-08 14:02 ` vincenzo.innocente at cern dot ch
2012-05-08 17:11 ` hubicka at gcc dot gnu.org
2012-05-09 7:30 ` vincenzo.innocente at cern dot ch
2012-05-09 9:15 ` rguenth at gcc dot gnu.org
2012-05-09 9:45 ` vincenzo.innocente at cern dot ch
2012-05-09 10:04 ` rguenth at gcc dot gnu.org
2012-05-09 10:16 ` vincenzo.innocente at cern dot ch
2012-05-09 10:17 ` rguenth at gcc dot gnu.org
2012-05-09 10:46 ` vincenzo.innocente at cern dot ch
2012-05-09 10:50 ` vincenzo.innocente at cern dot ch
2012-05-09 12:32 ` hubicka at ucw dot cz
2012-05-09 12:46 ` vincenzo.innocente at cern dot ch [this message]
2012-05-09 13:56 ` rguenth at gcc dot gnu.org
2012-05-09 15:01 ` vincenzo.innocente at cern dot ch
2012-05-10 7:16 ` [Bug lto/53282] [lto w/o linker plugin] " vincenzo.innocente at cern dot ch
2012-05-10 9:56 ` rguenth at gcc dot gnu.org
2012-05-10 10:17 ` vincenzo.innocente at cern dot ch
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-53282-4-DwEL7YYlzL@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).