-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.05.2013 06:39, xunxun wrote:
> And I don't know where is your problem, can you try my built :
> http://pcxprj.googlecode.com/files
> /MinGW64CRT_gcc4.7.3release_sse2static_win32.7z
>
I'm gearing towards 4.8.0, and shared. 4.8.0 is not really a r
--with-arch=pentium4 --with-tune=core-avx-i
I only use it for some popurse or perf. (Some lto needs -msse2, or will
cause compiler ICE.)
--enable-cxx-flags='-fno-function-sections -fno-data-sections'
At present, MinGW target linker can't support --gc-sections, so
-fno-function-sections -fno-data-s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.05.2013 18:11, Kai Tietz wrote:
> Well int clock_getcpuclockid we miss. I think it is obvious that we
> would like to provide it, so a patch to clock.c file would be desired
> here. The patch for an implementation for this function takes for
>
2013/5/3 Dongsheng Song
> Since Visual C++ 2005 (released in November 2005), time_t is now a
> 64-bit integer by default [1] . But mingw-w64 still use 32-bit integer
> by default on 32 bit Windows. I recommend use 64-bit integer by
> default on 3.0 CRT.
>
I agree with the spirit of this change,
Since Visual C++ 2005 (released in November 2005), time_t is now a
64-bit integer by default [1] . But mingw-w64 still use 32-bit integer
by default on 32 bit Windows. I recommend use 64-bit integer by
default on 3.0 CRT.
mingw-w64 use off_t 32-bit integer on 64 bit Windows, I think this is a mist
Well int clock_getcpuclockid we miss. I think it is obvious that we
would like to provide it, so a patch to clock.c file would be desired
here. The patch for an implementation for this function takes for
sure less time as it took you to collect all those information. So
why you weren't providing
On Thu, May 2, 2013 at 10:05 PM, Jim Michaels wrote:
>
> sorry, my yahoo mail can only top-post, so don't email me about that. still
> investigating this problem.
Yahoo mail has nothing to do with TOP posting. You have to configure
and maneuver the cursor in the mail but it works just the same.
2013/5/3 Ozkan Sezer
> On Fri, May 3, 2013 at 3:24 PM, JonY wrote:
> > On 5/3/2013 20:12, Ozkan Sezer wrote:
> >>>
> >>> You are right. That patch affects gcc's own compilation only. It
> >>> doesn't affects user-code.
> >>> Nevertheless for libstdc++-v3 uses - starting with 4.8 - by default
>
> -Original Message-
> From: Koehne Kai [mailto:kai.koe...@digia.com]
> Sent: Friday, May 03, 2013 2:29 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] format check broken
>
>
>
> > -Original Message-
> > From: Ozkan Sezer [mailto:seze...@gmail
> -Original Message-
> From: Ozkan Sezer [mailto:seze...@gmail.com]
> Sent: Friday, May 03, 2013 2:12 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] format check broken
>
> [...]
> Even then, it affects libstdc++ compilation itself. IMO, mingw[-w64] sho
On Fri, May 3, 2013 at 3:24 PM, JonY wrote:
> On 5/3/2013 20:12, Ozkan Sezer wrote:
>>>
>>> You are right. That patch affects gcc's own compilation only. It
>>> doesn't affects user-code.
>>> Nevertheless for libstdc++-v3 uses - starting with 4.8 - by default
>>> POSIX-printf due it relies badly
On 5/3/2013 20:12, Ozkan Sezer wrote:
>>
>> You are right. That patch affects gcc's own compilation only. It
>> doesn't affects user-code.
>> Nevertheless for libstdc++-v3 uses - starting with 4.8 - by default
>> POSIX-printf due it relies badly on this behavior internally.
>
> Even then, it aff
On Fri, May 3, 2013 at 1:23 PM, Kai Tietz wrote:
> 2013/5/3 Ozkan Sezer :
>> On Fri, May 3, 2013 at 1:09 PM, xunxun wrote:
>>> 于 2013/5/3 星期五 17:59, Ozkan Sezer 写道:
On Fri, May 3, 2013 at 12:51 PM, niXman wrote:
>
> Hi JonY,
>
>> If you use -D__MINGW_USE_ANSI_STDIO=1, u
2013/5/3 Ozkan Sezer :
> On Fri, May 3, 2013 at 1:09 PM, xunxun wrote:
>> 于 2013/5/3 星期五 17:59, Ozkan Sezer 写道:
>>>
>>> On Fri, May 3, 2013 at 12:51 PM, niXman wrote:
Hi JonY,
> If you use -D__MINGW_USE_ANSI_STDIO=1, use %lld.
> If you DO NOT USE -D__MINGW_USE_ANSI_STDIO=1,
On Fri, May 3, 2013 at 1:09 PM, xunxun wrote:
> 于 2013/5/3 星期五 17:59, Ozkan Sezer 写道:
>>
>> On Fri, May 3, 2013 at 12:51 PM, niXman wrote:
>>>
>>> Hi JonY,
>>>
If you use -D__MINGW_USE_ANSI_STDIO=1, use %lld.
If you DO NOT USE -D__MINGW_USE_ANSI_STDIO=1, use %I64d.
>>>
>>> Tell me pleas
于 2013/5/3 星期五 17:59, Ozkan Sezer 写道:
> On Fri, May 3, 2013 at 12:51 PM, niXman wrote:
>> Hi JonY,
>>
>>> If you use -D__MINGW_USE_ANSI_STDIO=1, use %lld.
>>> If you DO NOT USE -D__MINGW_USE_ANSI_STDIO=1, use %I64d.
>> Tell me please, what can be reasons to use '%I64d' and do not use
>> '-D__MINGW
On Fri, May 3, 2013 at 12:51 PM, niXman wrote:
> Hi JonY,
>
>> If you use -D__MINGW_USE_ANSI_STDIO=1, use %lld.
>> If you DO NOT USE -D__MINGW_USE_ANSI_STDIO=1, use %I64d.
>
> Tell me please, what can be reasons to use '%I64d' and do not use
> '-D__MINGW_USE_ANSI_STDIO=1' ?
> I'm just curious, why
> I'm just curious, why not just use the GNU style format string?
I'm just curious, why not just use the GNU style format string _by_default_?
--
Regards,
niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourcefo
Hi JonY,
> If you use -D__MINGW_USE_ANSI_STDIO=1, use %lld.
> If you DO NOT USE -D__MINGW_USE_ANSI_STDIO=1, use %I64d.
Tell me please, what can be reasons to use '%I64d' and do not use
'-D__MINGW_USE_ANSI_STDIO=1' ?
I'm just curious, why not just use the GNU style format string?
Thanks.
--
Reg
On 5/3/2013 10:05, Jim Michaels wrote:
>
> sorry, my yahoo mail can only top-post, so don't email me about that. still
> investigating this problem.
>
> when I try
>
> #include
> #include
> int main(void) {
> int64_t maxi=0x7fffLL;
> int64_t mini=0xLL;
>
20 matches
Mail list logo
