Hi,
The linker plugin with LTO seems not working. When I link a static library
which only contains LTO-enabled slim objects, the flag -fuse-linker-plugin
doesn't work. The linker always tell me some symbols are undefined.
Is it a bug?
What I use is:
x86_64-4.9.0-release-win32-sjlj-rt_v3-rev1
Are you using GCC 4.9.0?
Since GCC 4.9.0, LTO-enabled object file doesn't contain normal object code
but GIMPLE bytecode by default.
If you want to link to a static library, you have to pass
-fuse-linker-plugin to let it extract LTO segments, and AFAIK it's enabled
by default when -flto is
Then you must experience the same thing as I did.
2014-04-26 21:24 GMT+08:00 lh_mouse lh_mo...@126.com:
Yes gcc 4.9.0.
Thread model: win32
gcc version 4.9.0 (i686-win32-sjlj-rev0, Built by MinGW-W64 project)
2014-04-26
--
Best regards,
lh_mouse
2014/1/16 Alexey Pavlov alex...@gmail.com
Long time ago we add possibility to build Clang into mingw-builds scripts.
Now we want to provide Clang builds for mingw-w64 toolchains.
There are two possibilities that we can do:
*1. *Include clang builds into toolchain archive
*2.* Provide
Hi,
Some .o files are generated by windres, so you have to add
--target=pe-i386 to windres arguments in makefile.gcc.
2013/12/13 Marco N nic...@list.ru
Dear subscribers,
I admit that I am not an expert in using gcc/ld and especially their
flags. Anyway I used them from time time and I
Hi,
Is it possible that only build the runtimes like libstdc++, libgcc_s_sjlj-1
with LTO enabled?
Someone static link it with LTO can benefit form it.
Thanks!
2013/9/24 xunxun xunxun1...@gmail.com
于 2013/9/24 星期二 22:21, Alexey Pavlov 写道:
2013/9/24 xunxun xunxun1...@gmail.com:
于 2013/9/24
I often get lots of internal compilation error with LTO, too.
What make things more weird is that sometimes add LTO related options like
-flto-partition=none can remove the problem and sometimes it can not.
Thanks!
2013/9/24 Alexey Pavlov alex...@gmail.com
2013/9/24 TOCK Chiu stanley82
You may specify the include folder by pass -I parameter to GCC.
I think this is a better solution because it won't mess the environment
variables up.
For example pass -IC:\Users\Arbol
One\Documents\dev\C++\Applications\development\intence\ruch\Donald
Hi,
There is a problem in Ruben's builds
x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb.7z and
x86_64-w64-mingw32-gcc-4.8.0-linux64_rubenvb.tar.xz. The simple code
snippet below with argument -static -O2 -flto can reproduce the problem:
#includeiostream
int main(){
std::cout Foo = 101 std::endl;
Hi,
There is a problem in Ruben's builds
x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb.7z and
x86_64-w64-mingw32-gcc-4.8.0-linux64_rubenvb.tar.xz. The simple code
snippet below with argument -static -O2 -flto can reproduce the problem:
#includeiostream
int main(){
std::cout Foo = 101 std::endl;
10 matches
Mail list logo