Re: [Mingw-w64-public] Mass rebuild report for July 15 2013

2013-07-17 Thread Jacek Caban
On 07/15/13 23:50, Erik van Pienbroek wrote: mingw-wine-gecko-2.21-1 Build logs: http://build1.vanpienbroek.nl/fedora-mingw-rebuild/20130715/mingw-wine-gecko-2.21-1 Also winpthreads related. Bug has already been reported upstream and a patch is pending approval:

Re: [Mingw-w64-public] Interlocked* patches follow-up

2013-07-17 Thread Jacek Caban
On 07/17/13 01:12, dw wrote: Please review the new patch Well, we got your good news and your bad news. On the plus side, this patch fixes the problem I was seeing with -Os. On the downside, my release build script also uses -fwhole-program. This is giving me a link error: /undefined

Re: [Mingw-w64-public] Interlocked* patches follow-up

2013-07-17 Thread dw
Kai, can you offer some compiler insight here? Something is getting tangled here, but I'm not quite sure what. I can't reproduce it here. It looks like a GCC bug, but I'm not familiar with those constprop symbols. Maybe Kai will have some idea. I've had someone else try, and they see the

Re: [Mingw-w64-public] [Patch] _bittest, _bittestandset, etc

2013-07-17 Thread dw
Ping. These have nothing to do with the boost/Interlocked* issues. dw On 7/15/2013 2:37 PM, dw wrote: 1) Move these functions to intrin-impl.h: _bittest, _bittest64 _bittestandset, _bittestandreset, _bittestandcomplement _bittestandset64, _bittestandreset64, _bittestandcomplement64 2)

Re: [Mingw-w64-public] Interlocked* patches follow-up

2013-07-17 Thread Kai Tietz
Hi this issue seems t be related to a bug fixed for gcc' trunk and for the 4.8 branch. Could you test more recent version to see if issue remains? Kai Am 17.07.2013 14:14 schrieb dw limegreenso...@yahoo.com: Kai, can you offer some compiler insight here? Something is getting tangled here,