Re: [Mingw-w64-public] Regression in trunk regarding InterlockedCompareExchange

Erik van Pienbroek schreef op vr 14-06-2013 om 19:28 [+0200]: For now I've managed to workaround the regression by partially reverting r5713. This change makes intrincs/ilockcxch.c part of libmingwex instead of libkernel32 (as it was before r5713). I'm using this patch now in the Fedora

[Mingw-w64-public] MinGW-w64 web page

Hi, I noticed the front page changed, removing all previous links to the binary toolchains in the MinGW-w64 sourceforge downloads area. Why did this happen, and can these please be readded? Thanks, Ruben -- This SF.net

Re: [Mingw-w64-public] MinGW-w64 web page

Also, there is no way to get from mingw-w64.sourceforge.net to http://sourceforge.net/projects/mingw-w64/files Or the SVN Sourceforge info page thingie. 2013/6/16 Ruben Van Boxem vanboxem.ru...@gmail.com Hi, I noticed the front page changed, removing all previous links to the binary

[Mingw-w64-public] There is no MinGW-w64 stable release that can be used to build GCC 4.8*

Hi, It was great that Jon_Y fixed up the POSIX printf stuff so that GCC 4.8 can finally just use std::to_string etc... But the changes in GCC mean that you cannot build GCC 4.8+ with a currently released MinGW-w64 version. I would have hoped that there would be a new release by now, until all

Re: [Mingw-w64-public] dllexport/inline pessimization (hack included)

Hello Kai. Kai Tietz ktiet...@googlemail.com writes: [snip] Thanks for looking into this and for improving my knowledge of GCC. I must admit that I found GCC sources quite arcane. It reminds me of Emacs sources. No wonder, both were started by the same person :-) I tried your patch with one of

Re: [Mingw-w64-public] MinGW-w64 web page

On Sun, Jun 16, 2013, Ruben Van Boxem wrote: Also, there is no way to get from mingw-w64.sourceforge.net to http://sourceforge.net/projects/mingw-w64/files Or the SVN Sourceforge info page thingie. 2013/6/16 Ruben Van Boxem vanboxem.ru...@gmail.com Hi, I noticed the front

Re: [Mingw-w64-public] There is no MinGW-w64 stable release that can be used to build GCC 4.8*

On 6/16/2013 23:18, Ruben Van Boxem wrote: Hi, It was great that Jon_Y fixed up the POSIX printf stuff so that GCC 4.8 can finally just use std::to_string etc... But the changes in GCC mean that you cannot build GCC 4.8+ with a currently released MinGW-w64 version. Yes, this is a known

Re: [Mingw-w64-public] What is the purpose of intrin.h?

Eg. In file guard is for each function: So, I see 2 cases for the code you sent: 1) In user code, they can just #include intrin.h. There are no special defines they need to create. By default, it will create inline definitions for all intrinsics. 2) In files like intrinsic\__stosb.c,