2010/9/12 JonY <[email protected]>
>
> I have no idea how to actually debug lto.
>
Neither do I, but I have an update to my progress: I have built a 4.6 GCC
using the latest mingw-w64 autobuild (without lto), and this fresh compiler
can do lto, so I can continue my search.
I am currently stopped by:
> Creating library file: ./shlib/libgcc_s.a.tmp
> lto1.exe: error: bad value (core2) for -mtls-dialect= switch
> lto-wrapper: M:\Development\msys\home\Ruben\mingw64\build\gcc\gcc\xgcc.exe
> returned 1 exit status
> collect2: lto-wrapper returned 1 exit status
>
when GCC was configured with:
> ../../src/gcc/configure --prefix=/home/ruben/mingw64/build/mingw64
> --with-sysroot=/home/ruben/mingw64/build/mingw64 --target=x86_64-w64-mingw32
> --host=x86_64-w64-mingw32 --build=x86_64-w64-mingw32 --with-gmp=/gcc-libs
> --with-mpfr=/gcc-libs -with-mpc=/gcc-libs --enable-languages=c,c++,lto
> --enable-stage1-languages=c,lto --enable-fully-dynamic-string
> --disable-multilib --enable-lto --disable-werror CFLAGS="-mtune=core2 -flto"
> LFLAGS="-flto -fwhopr=2"
Which tells me that -mtune=core2 is problematic for stage1 lto here. I will
now try to start with a fresh reconfigure without the -mtune=core2 CFLAG.
Does anyone know how to remove his flag from bootstrapping compilers, but
have it enabled for the final stage (the one built last)?
Thanks,
Ruben
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
