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;
//__int128 i=0x7fff;//gives er
-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: SHA1
>
>On 01.05.2013 22:09, swigg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clock_gettime() currently supports these clocks:
CLOCK_REALTIME (GetSystemTimeAsFileTime)
CLOCK_MONOTONIC (QueryPerformanceCounter)
CLOCK_PROCESS_CPUTIME_ID (GetProcessTimes)
CLOCK_THREAD_CPUTIME_ID (GetThreadTimes)
[1] states that if _POSIX_CPUTIME i
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.05.2013 22:08, Ruben Van Boxem wrote:
> 2013/5/2 LRN
>
>> I'm looking at your gcc configure, and things that caught my attention are:
>> --disable-sjlj-exceptions
>> I'm enabling them instead. My gcc uses sjlj instead of dw
>>
>
> Don't do thi
On 5/2/2013 12:08 PM, Ruben Van Boxem wrote:
2013/5/2 LRN mailto:lrn1...@gmail.com>>
I'm enabling them instead. My gcc uses sjlj instead of dw
Don't do this for x64 GCC 4.8. It has a fancy new seh implementation
which beats both alternatives in speed and compatibility.
On reading this,
2013/5/2 LRN
> On 01.05.2013 18:56, xunxun wrote:
> > 于 2013/5/1 星期三 21:15, LRN 写道:
> >> On 01.05.2013 10:32, xunxun wrote:
> >>> On Wed, May 1, 2013 at 3:13 AM, LRN wrote:
> On 30.04.2013 19:18, xunxun wrote:
> > 于 2013/4/24 星期三 19:12, LRN 写道:
> >> msgmerge.exe (from gettext, i gue
On 01.05.2013 18:56, xunxun wrote:
> 于 2013/5/1 星期三 21:15, LRN 写道:
>> On 01.05.2013 10:32, xunxun wrote:
>>> On Wed, May 1, 2013 at 3:13 AM, LRN wrote:
On 30.04.2013 19:18, xunxun wrote:
> 于 2013/4/24 星期三 19:12, LRN 写道:
>> msgmerge.exe (from gettext, i guess) hangs up, consuming 100%
11 matches
Mail list logo
