This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: LTO with cross compiler and static linking

On 03/19/2013 05:42 PM, Andrew Pinski wrote:
On Tue, Mar 19, 2013 at 9:28 AM, Sebastian Huber
<> wrote:
On 03/19/2013 04:50 PM, Andrew Pinski wrote:

On Tue, Mar 19, 2013 at 3:30 AM, Sebastian Huber
<>  wrote:


I test currently the GCC 4.8 release candidate.  Some GCC LTO tests fail
me since the introduction of LTO in GCC.  I use Binutils 2.23.1 for
EABI (powerpc-rtems4.11 target) configured with:

/scratch/archive/binutils-2.23.1/configure --target=powerpc-rtems4.11
--prefix=/scratch/install-4.8.0-RC-20130316 --disable-werror

For GCC I use:

/scratch/archive/gcc-4.8.0-RC-20130316/configure --disable-werror
--enable-threads=rtems --with-gnu-as --disable-multilib --enable-lto
--enable-newlib-mb --enable-newlib-iconv --with-gnu-ld --with-newlib
--verbose --with-system-zlib --disable-nls
--enable-version-specific-runtime-libs --enable-languages=c,c++
--target=powerpc-rtems4.11 --prefix=/scratch/install-4.8.0-RC-20130316

The easiest fix is inside the GCC testsuite itself.  In
testsuite/gcc.c-torture/execute/builtins/builtins.exp change:
if { [istarget *-*-eabi*]
       || [istarget *-*-elf] } {
     lappend additional_flags "-Wl,--allow-multiple-definition"
if { [istarget *-*-eabi*]
       || [istarget *-*-elf]
       || [istarget *-*-rtems*]} {
     lappend additional_flags "-Wl,--allow-multiple-definition"

Ok, so you say that this multiple definition with LTO is intentional for
statically linked applications?

For this set of testcases yes.  They are explicitly having multiple
defined symbols.

Just for reference there is also a GCC PR for this topic:

Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  :
PGP     : Public key available on request.

Diese Nachricht ist keine geschÃftliche Mitteilung im Sinne des EHUG.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]