Re: [Mingw-w64-public] gcc-4.8.1 build failure libstdc++ string

2013-06-24 Thread Alon Bar-Lev
On Tue, Jun 25, 2013 at 5:29 AM, Alexey Pavlov wrote: > > > > 2013/6/25 Alon Bar-Lev >> >> On Tue, Jun 25, 2013 at 12:00 AM, Ruben Van Boxem >> wrote: >> > >> > 2013/6/22 Alon Bar-Lev >> >> >> >> Hello, >> >> >> >> gcc-4.8.1 failing for some reason, I guess std::vswprintf is >> >> incompatible

Re: [Mingw-w64-public] Fast sprintf and 15 times slower std::sprintf

2013-06-24 Thread Albus X
Thank you for your response, here is my test result: /d/Downloads/mingw $ cat sprintf.cc #include #define MAX 50 int main () { int i; for (i = 0; i < MAX; i++){ charx[100]; sprintf(x, "x%dx%dx", i, i<<2); } } /d/Downloads/mingw $ cat stdsprintf.cc #incl

Re: [Mingw-w64-public] gcc-4.8.1 build failure libstdc++ string

2013-06-24 Thread Alexey Pavlov
2013/6/25 Alon Bar-Lev > On Tue, Jun 25, 2013 at 12:00 AM, Ruben Van Boxem > wrote: > > > > 2013/6/22 Alon Bar-Lev > >> > >> Hello, > >> > >> gcc-4.8.1 failing for some reason, I guess std::vswprintf is > incompatible for some reason, gcc-4.7.3 works correctly. Using > mingw64-runtime-2.0.8. >

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

2013-06-24 Thread dw
So, I have finished the changes I had in mind for this. I have tried to be clear about how I intend things to work (IOW, there's lots of comments). Changing headers/includes without breaking something elsewhere can be challenging, but I'm pretty sure I've got this right. On the plus side, if

Re: [Mingw-w64-public] Fast sprintf and 15 times slower std::sprintf

2013-06-24 Thread Derek Buitenhuis
On 2013-06-24 5:08 PM, Ruben Van Boxem wrote: > IMHO, this needs to be looked into and optimized. Could you test an old build > that uses the v2.x runtime to see if that changes anything. Unfortunately, I > wouldn't be able to point you to one of my builds that uses this. I guess GCC > 4.7.2 or

Re: [Mingw-w64-public] Fast sprintf and 15 times slower std::sprintf

2013-06-24 Thread Ruben Van Boxem
2013/6/22 Albus X > Hello. I experienced a strange efficiency problem in my code and after > some debuging I find that std::sprintf is very slow. Indeed it's even > different from the sprintf function in . > > When doing the following test: > > #include > // #include > // using std:

Re: [Mingw-w64-public] gcc-4.8.1 build failure libstdc++ string

2013-06-24 Thread Alon Bar-Lev
On Tue, Jun 25, 2013 at 12:00 AM, Ruben Van Boxem wrote: > > 2013/6/22 Alon Bar-Lev >> >> Hello, >> >> gcc-4.8.1 failing for some reason, I guess std::vswprintf is incompatible >> for some reason, gcc-4.7.3 works correctly. Using mingw64-runtime-2.0.8. >> >> Example (libstdc++-v3/include/bits/ba

Re: [Mingw-w64-public] gcc-4.8.1 build failure libstdc++ string

2013-06-24 Thread Ruben Van Boxem
2013/6/22 Alon Bar-Lev > Hello, > > gcc-4.8.1 failing for some reason, I guess std::vswprintf is incompatible > for some reason, gcc-4.7.3 works correctly. Using mingw64-runtime-2.0.8. > > Example (libstdc++-v3/include/bits/basic_string.h): > inline wstring > to_wstring(int __val) > { retur

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread NightStrike
On Mon, Jun 24, 2013 at 1:37 AM, Ozkan Sezer wrote: > On Sun, Jun 23, 2013 at 4:15 PM, Ruben Van Boxem > wrote: >> Hi everyone, >> >> I have come to the conclusion that my MinGW-w64 builds bring too little to >> the table for me to continue maintaining them. >> >> I strongly encourage you to use

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread forumer
I wanted to compile GNUStep(objc) on windows because I would like to debug something and thus I prefer compile everything on windows and not cross-compile from linux. A few years ago I have built an environment(called MaxGW :-) consisting in the msys+mingw and their package manager mingw-get but

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread Ruben Van Boxem
2013/6/24 Ozkan Sezer > On Mon, Jun 24, 2013 at 10:51 AM, Kai Tietz > wrote: > > Hello Ruben, > > > > 2013/6/23 Ruben Van Boxem : > >> Hi everyone, > >> > >> I have come to the conclusion that my MinGW-w64 builds bring too little > to > >> the table for me to continue maintaining them. > >> > >>

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread Ozkan Sezer
On Mon, Jun 24, 2013 at 10:51 AM, Kai Tietz wrote: > Hello Ruben, > > 2013/6/23 Ruben Van Boxem : >> Hi everyone, >> >> I have come to the conclusion that my MinGW-w64 builds bring too little to >> the table for me to continue maintaining them. >> >> I strongly encourage you to use the plethora of

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread Kai Tietz
Hello Ruben, 2013/6/23 Ruben Van Boxem : > Hi everyone, > > I have come to the conclusion that my MinGW-w64 builds bring too little to > the table for me to continue maintaining them. > > I strongly encourage you to use the plethora of toolchains in a multitude of > configurations available at min

Re: [Mingw-w64-public] End of rubenvb builds

2013-06-24 Thread Ruben Van Boxem
2013/6/24 Ozkan Sezer > On Sun, Jun 23, 2013 at 4:15 PM, Ruben Van Boxem > wrote: > > Hi everyone, > > > > I have come to the conclusion that my MinGW-w64 builds bring too little > to > > the table for me to continue maintaining them. > > > > I strongly encourage you to use the plethora of toolc