Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-28 Thread Christer Solskogen
On 27.01.2019 20:18, Mateusz wrote: W dniu 27.01.2019 o 18:40, Christer Solskogen pisze: On 26.01.2019 01:01, Mateusz wrote: For me it looks OK. Which version of binutils? It's fixed in master branch. $ gcc -v && ld -v Using built-in specs. COLLECT_GCC=f:\msys\m64-83\bin\gcc.exe

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-27 Thread Mateusz
W dniu 27.01.2019 o 18:40, Christer Solskogen pisze: > On 26.01.2019 01:01, Mateusz wrote: > >> For me it looks OK. > > Which version of binutils? It's fixed in master branch. $ gcc -v && ld -v Using built-in specs. COLLECT_GCC=f:\msys\m64-83\bin\gcc.exe

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-27 Thread Christer Solskogen
On 26.01.2019 01:01, Mateusz wrote: For me it looks OK. Which version of binutils? It's fixed in master branch. And was the native compiler cross compiled from Linux? Try with a simple hello world in C (or C++) (without the #define) ___

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-25 Thread Mateusz
W dniu 25.01.2019 o 10:48, Christer Solskogen pisze: > On 25.01.2019 10:43, Mateusz wrote: >> W dniu 21.01.2019 o 21:20, Christer Solskogen pisze: >>> I've successfully built a multilib compiler on linux targeting both >>> x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile a

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-25 Thread Christer Solskogen
On 25.01.2019 10:43, Mateusz wrote: W dniu 21.01.2019 o 21:20, Christer Solskogen pisze: I've successfully built a multilib compiler on linux targeting both x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile a native Windows compiler (what do you really call that? Crossed

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-25 Thread Mateusz
W dniu 21.01.2019 o 21:20, Christer Solskogen pisze: > I've successfully built a multilib compiler on linux targeting both > x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile a > native Windows compiler (what do you really call that? Crossed compiler? > Hosted?) with

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-24 Thread Christer Solskogen
On 23.01.2019 03:26, Liu Hao wrote: I have CC'd binutils ML. Hope someone there would know something about GAS. It's now fixed in binutils. The question is why does --enable-experimental produce a assembler like that? ___ Mingw-w64-public

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-22 Thread Christer Solskogen
On 23.01.2019 05:35, Alan Modra wrote: On Wed, Jan 23, 2019 at 10:26:06AM +0800, Liu Hao wrote: 在 2019/1/22 上午4:20, Christer Solskogen 写道: I've successfully built a multilib compiler on linux targeting both x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile a native

Re: [Mingw-w64-public] --enable-experimental breaks as

2019-01-22 Thread Liu Hao
在 2019/1/22 上午4:20, Christer Solskogen 写道: > I've successfully built a multilib compiler on linux targeting both > x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile > a native Windows compiler (what do you really call that? Crossed > compiler? Hosted?) with mingw-w64-crt

[Mingw-w64-public] --enable-experimental breaks as

2019-01-21 Thread Christer Solskogen
I've successfully built a multilib compiler on linux targeting both x86_64-w64-mingw32 and i686-w64-mingw32. Using that compiler to compile a native Windows compiler (what do you really call that? Crossed compiler? Hosted?) with mingw-w64-crt configured with "--enable-experimental" I get this