> shame that the msvc (and subsequently mingw) does a
> #define MAXIMUM_PROCESSORS 32
> it seems these days that limits are meant to be broken,
That #define certainly does not mean that code built with mingw (or
msvc) would be limited to running threads on a maximum of 32
concurrent processors, if
does. I suppose they will fix it AFTER
somebody comes out with such a processor. :-(
If there's a limit, somebody is going to push it.
From: Doug Semler
To: mingw-w64-public@lists.sourceforge.net
Sent: Sun, March 7, 2010 12:26:46 PM
Subject: Re:
On Sun, 07 Mar 2010 14:59:50 Kai Tietz wrote:
> 2010/3/7 Doug Semler :
> > On Thu, 04 Mar 2010 17:20:07 Jim Michaels wrote:
> >> in MSVC,
> >> __int64 x=12345678901234567i64;
> >>
> >> point 1: this type __int64 doesn't require me to #include to
> >> define it. in mingw and mingw-w64, one must #
2010/3/7 Doug Semler :
> On Thu, 04 Mar 2010 17:20:07 Jim Michaels wrote:
>> in MSVC,
>> __int64 x=12345678901234567i64;
>>
>> point 1: this type __int64 doesn't require me to #include to
>> define it. in mingw and mingw-w64, one must #include . why?
>>
>> point 2: there are also __int32 __int16
On Thu, 04 Mar 2010 17:20:07 Jim Michaels wrote:
> in MSVC,
> __int64 x=12345678901234567i64;
>
> point 1: this type __int64 doesn't require me to #include to
> define it. in mingw and mingw-w64, one must #include . why?
>
> point 2: there are also __int32 __int16 and __int8 types.
If I rememb
On Fri, Mar 5, 2010 at 12:20 AM, Jim Michaels wrote:
> in MSVC,
> __int64 x=12345678901234567i64;
>
> point 1: this type __int64 doesn't require me to #include to
> define it. in mingw and mingw-w64, one must #include . why?
It is enough, I guess.. Include windows.h if you want,
why is that a p
in MSVC,
__int64 x=12345678901234567i64;
point 1: this type __int64 doesn't require me to #include to define
it. in mingw and mingw-w64, one must #include . why?
point 2: there are also __int32 __int16 and __int8 types.
point 3: mingw does not utilize the i64 constant thingy (whatever it's
