Re: [Mingw-w64-public] [Mingw-users] Mingw64 and CMake

On 7/11/2011 14:08, Maxime Lecourt wrote: > Hello, > > I want to install mingw64 on my windows seven computer. > I don't have autotools, but I have cmake installed. > Is there somewhere a version of Mingw64 with CMake scripts ? > And can I compile mingw64 using mingw32 compiler ? > > Regards, >

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 19:13, Kai Tietz 写道: Another thing missing here is the use of lock as prefix ... I update to winpthreads svn 4271: this is a debug log GNU gdb (pcx32) 7.3.50.20110709 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 19:13, Kai Tietz 写道: > Another thing missing here is the use of lock as prefix Er.. I have to go out for some moment and sorry... -- Best Regards, PcX -- All of the data generated in your IT infrastructure i

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 19:11, Kai Tietz 写道: > 2011/7/11 PcX: >> 于 2011/7/11 19:02, Kai Tietz 写道: >>> So I don't understand here this ill-instruction failure you see. xadd >>> (which is used here underhood for .InterlockedDecrement is present >>> beginning with i486. see >>> http://asm.inightmare.org/opcodel

Re: [Mingw-w64-public] winpthread build with static edition

Another thing missing here is the use of lock as prefix ... -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats,

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 19:02, Kai Tietz 写道: >> >> So I don't understand here this ill-instruction failure you see.  xadd >> (which is used here underhood for .InterlockedDecrement is present >> beginning with i486.  see >> http://asm.inightmare.org/opcodelst/index.php?op=XADD > > It's very s

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 19:02, Kai Tietz 写道: > So I don't understand here this ill-instruction failure you see. xadd > (which is used here underhood for .InterlockedDecrement is present > beginning with i486. see > http://asm.inightmare.org/opcodelst/index.php?op=XADD It's very strange. I write : __

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 18:57, Kai Tietz 写道: >> >> What funny CPU you are using? It seems that xadd isn't supported by it. > > Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz 2.20 GHz > > -- > Best Regards, > PcX So I don't understand here this ill-instruction failure you see. xadd (which is use

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 18:57, Kai Tietz 写道: > What funny CPU you are using? It seems that xadd isn't supported by it. Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz 2.20 GHz -- Best Regards, PcX -- All of the data generated in your I

Re: [Mingw-w64-public] winpthread build with static edition

What funny CPU you are using? It seems that xadd isn't supported by it. Regards, Kai -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application perfor

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 18:38, Kai Tietz 写道: Well, it might be interesting to see here content of _pthread_tls variable. You can use in gdb the command 'print _pthread_tls' for this. What happens if you simple continue after this trace-point? (This is done by command 'c' in gdb). Here is: (gdb) p _pthread_

Re: [Mingw-w64-public] winpthread build with static edition

Well, it might be interesting to see here content of _pthread_tls variable. You can use in gdb the command 'print _pthread_tls' for this. What happens if you simple continue after this trace-point? (This is done by command 'c' in gdb). Kai 2011/7/11 PcX : > 于 2011/7/11 17:15, Kai Tietz 写道: >> >>

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 17:15, Kai Tietz 写道: You need to configure gcc with --enable-threads=posix to have full feature-set enabled for winpthread. Sorry, I'm not familiar with some gdb commands, so I type "step 1" here. This is the debug log: GNU gdb (pcx32) 7.3.50.20110709 Copyright (C) 2011 Free Sof

Re: [Mingw-w64-public] float.h patch to accomodate Clang

Thanks, patch applied to trunk. Committed at revision 4272. Kai -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security thre

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 17:19, Kai Tietz 写道: > Yes, this is for sure something good, as it pre-initialize memory here. OK, I'll try again. I will go to dinner, and after that, I will email to you. Wait for my information please. Thanks. -- Best Regards, PcX -

Re: [Mingw-w64-public] winpthread build with static edition

Yes, this is for sure something good, as it pre-initialize memory here. Kai 2011/7/11 PcX : > 于 2011/7/11 17:15, Kai Tietz 写道: >> >> You need to >> configure gcc with --enable-threads=posix to have full feature-set >> enabled for winpthread.  Then you shouldn't have issues about gomp, >> too. > >

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 17:15, Kai Tietz 写道: > You need to > configure gcc with --enable-threads=posix to have full feature-set > enabled for winpthread. Then you shouldn't have issues about gomp, > too. And do I need change "team = gomp_malloc (size)" to "team = gomp_malloc_cleared (size)"? -- Best Regar

Re: [Mingw-w64-public] winpthread build with static edition

I see your issue. You are trying to use posix implementation of gomp with gthr-win32.h implementation of threading ... You need to configure gcc with --enable-threads=posix to have full feature-set enabled for winpthread. Then you shouldn't have issues about gomp, too. Regards, Kai 2011/7/11 K

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 16:58, Kai Tietz 写道: here does this line come from? I don't find '__ptr = TlsGetValue (__key);' in my source tree. Neither in winpthread, nor in crt-TLS code. As this log: GNU gdb (pcx32) 7.3.50.20110709 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL versi

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 16:06, Kai Tietz 写道: >> >> I mean change "team = gomp_malloc (size)" to "team = gomp_malloc_cleared >> (size)" > > I do that, but seem not be functional. > It's debug log. > It stops at 611      __ptr = TlsGetValue (__key); > Then it seems to enter an endless lopp. Wh

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 16:06, Kai Tietz 写道: I mean change "team = gomp_malloc (size)" to "team = gomp_malloc_cleared (size)" I do that, but seem not be functional. It's debug log. It stops at 611 __ptr = TlsGetValue (__key); Then it seems to enter an endless lopp. -- Best Regards, PcX debug.log De

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 14:15, Kai Tietz 写道: >> >> See in team.c the function gomp_new_team. Use here instead for 'team = >> gomp_malloc (size);' the following 'team = gomp_malloc_cleared (size);'. > > You mean change "team = gomp_malloc (size)" to "team = gomp_malloc_cleared > (size)", or af

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 14:15, Kai Tietz 写道: > See in team.c the function gomp_new_team. Use here instead for 'team = > gomp_malloc (size);' the following 'team = gomp_malloc_cleared (size);'. You mean change "team = gomp_malloc (size)" to "team = gomp_malloc_cleared (size)", or after ""team = gomp_malloc (

Re: [Mingw-w64-public] clang++ exe fails to run on 64-Bit Windows 7

Op 11 jul. 2011 02:59 schreef "Beman Dawes" het volgende: > > Ruben Van Boxem writes: > > > > >... > > > > Yes, I'm aware of the problem. Clang++ is just a renamed version of clang.exe, > so just copy clang.exe to clang++.exe and all will work as it should (it uses > the image name to set c++ set

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 15:17, Kai Tietz 写道: > > could you test this modification and see > > You say the libgomp modification ? > I have to recompile gcc... > > -- > Best Regards, > PcX Well, for first step you need just to recompile libgomp (and possible dependent libraries). A complete bo

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 15:17, Kai Tietz 写道: could you test this modification and see You say the libgomp modification ? I have to recompile gcc... -- Best Regards, PcX -- All of the data generated in your IT infrastructure is ser

Re: [Mingw-w64-public] winpthread build with static edition

2011/7/11 PcX : > 于 2011/7/11 14:15, Kai Tietz 写道: >> >> So I looked a bit into libgomp's source code and I see that I might have >> found the cause for this crash. See in team.c the function gomp_new_team. >> Use here instead for 'team = gomp_malloc (size);' the following 'team = >> gomp_malloc_cl

Re: [Mingw-w64-public] winpthread build with static edition

于 2011/7/11 14:15, Kai Tietz 写道: > So I looked a bit into libgomp's source code and I see that I might > have found the cause for this crash. See in team.c the function > gomp_new_team. Use here instead for 'team = gomp_malloc (size);' the > following 'team = gomp_malloc_cleared (size);'. This m