> > 2010/9/11 John E. / TDM <[email protected]> > On 9/11/2010 12:19 PM, Kai Tietz wrote: > > > , but nevertheless libelf (which > > isn't an elf OS specific library btw) is required so that LTO works as > > it should. > > Trust me, it isn't! I have never installed libelf on my build machine, >> but LTO is enabled and I see dramatic improvements when I use it. >> >> >> ------------------------------------------------------------------------------ >> 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 >> > I don't think the absence of libelf is the problem here. There are no missing include files, and no ld error messages about undefined references or missing libs. It's the lto-wrapper that has some odd buffer reading problem (lto1 tries to read 0 bytes beyond end of buffer.... nothing wrong with that?) when compiling libgcc_s with an intermediate compiler called xgcc. Just for the record, this is what I'm using: gmp 5.0.1 mpfr 3.0.0 mpc 0.8.2 libiconv 1.13.1 binutils 2.20.51 gcc 4.6-20100904 mingw-w64 20100909 (libelf 0.8.9) ...
Now I've gotten further by removing my CFLAGS="-flto" and LFLAGS="-flto" (I'll have to find out how to get them working for the final compile; is there something like STAGE3_CFLAGS and --enable-stage2-languages=c,c++,lto?). I had to copy TDM64's pthread library and header to the sysroot directory, and libgomp built fine (still stage1 I think). Now I get an error in libcpp: ../../../src/gcc/libcpp/files.c: In function 'read_file_guts': ../../../src/gcc/libcpp/files.c:609:7: error: comparison is always false due > to limited range of data type [-Werror=type-limits]For now I have > reconfigured with --disable-werror to work around this. > A new question has also popped into my mind: for x86_64, is something like -march=k8 automatically enabled for? Because it should be, as -march=k8 is equivalent to the x86_64 instruction set, if I read the docs correctly. 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
