> -Original Message-
> From: Jim Michaels [mailto:jmich...@yahoo.com]
> Sent: Monday, May 06, 2013 9:12 AM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] format check broken
>
> what is %lldb? never heard of it. I don't see it i
what is %lldb? never heard of it. I don't see it in the gcc manual.
>
> From: Koehne Kai
>To: "mingw-w64-public@lists.sourceforge.net"
>
>Sent: Friday, May 3, 2013 5:28 AM
>Subject: Re: [Mingw-w64-public] format check broken
compatibility with msvc++. that's what the mingw compiler is supposed to
emulate, yes?
>
> From: niXman
>To: mingw-w64-public@lists.sourceforge.net
>Sent: Friday, May 3, 2013 2:52 AM
>Subject: Re: [Mingw-w64-public] format check bro
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-
>
> -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
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;
>
lists.sourceforge.net"
>
>Sent: Thursday, May 2, 2013 5:22 PM
>Subject: Re: [Mingw-w64-public] format check broken
>
>
>
>%I64d results in same message.
>
>
>
>
>>________________
>> From: LRN
>>To: mingw-w64-public@lists.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.05.2013 04:22, Jim Michaels wrote:
> On Thursday, May 2, 2013 3:28 PM, LRN wrote:
>> On 01.05.2013 22:09, swigger wrote:
>>> ~/tmp$ cat hello.c
>>> #include
>>>
>>> int main()
>>> {
>>> printf("%lld\n", 0x123456789all);
>>> ret
%I64d results in same message.
>
> From: LRN
>To: mingw-w64-public@lists.sourceforge.net
>Sent: Thursday, May 2, 2013 3:28 PM
>Subject: Re: [Mingw-w64-public] format check broken
>
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01.05.2013 22:09, swigger wrote:
> ~/tmp$ cat hello.c
> #include
>
> int main()
> {
> printf("%lld\n", 0x123456789all);
> return 0;
> }
> ~/tmp$ gcc -Wall hello.c
> ~/tmp$ i686-w64-mingw32-gcc -Wall hello.c
> hello.c: In function ‘
On 5/2/2013 02:09, swigger wrote:
> ~/tmp$ cat hello.c
> #include
>
> int main()
> {
> printf("%lld\n", 0x123456789all);
> return 0;
> }
> ~/tmp$ gcc -Wall hello.c
> ~/tmp$ i686-w64-mingw32-gcc -Wall hello.c
> hello.c: In function ‘main’:
> hello.c:5:2: warning: unknown conversion
~/tmp$ cat hello.c
#include
int main()
{
printf("%lld\n", 0x123456789all);
return 0;
}
~/tmp$ gcc -Wall hello.c
~/tmp$ i686-w64-mingw32-gcc -Wall hello.c
hello.c: In function ‘main’:
hello.c:5:2: warning: unknown conversion type character ‘l’ in format
[-Wformat=]
printf("%lld\n
22 matches
Mail list logo
