Hi, thanks for the quick response. I will try to get a backtrace though last time I tried I remember I got some assembly mumbo-jumbo, related to openmp for certain(If memory serves right, something like omp_get_thread_name hit a null pointer or something similar). Unfortunately I don't have a unix 4.7 to verify the bug there, but regular MinGW 4.6.2 works fine. I would prefer to stick with 4.7 or 4.6.3 if possible.
I was refering to optimization in terms of use of the compiler by a broad team of builders, not in terms of producing the buggy behaviour. quoting: """ 1) release: released GCC versions, with the then latest MinGW-w64 CRT together with trunk binutils/gdb will be placed here. The two latter things are pretty much rock-solid, and binutils releases very little, so this makes sense. GCC will use plain "win32" threading, but the pthreads-based stuff in GCC (think libgomp) is still based on winpthreads. This should resolve all issues people are having with the posix-threading builds I've been pushing previously. This does mean no <thread> for C++. """ This may well be the source of our problems """ ....As before, these are now built with -mtune=corei7 and a bunch of other fancy optimization options I hope work as advertised. """ This may be troublesome for people who don't own an i7 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
