This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: Testresults of libffi-3.0.9rc10 for x64 mingw target
2009/12/28 Timothy Wall <twall@users.sf.net>:
>
> On Dec 28, 2009, at 12:50 PM, Andrew Haley wrote:
>
>> On 12/28/2009 05:16 PM, Anthony Green wrote:
>>>
>>> On 12/27/2009 05:34 PM, Kai Tietz wrote:
>>>>
>>>> Hello,
>>>>
>>>> this are the test-results for x86_64-pc-mingw32 target
>>>>
>>>> ? ? ? ? ? ? ? ?=== libffi Summary ===
>>>>
>>>> # of expected passes ? ? ? ? ? ?1526
>>>> # of unexpected failures ? ? ? ?38
>>>> # of unexpected successes ? ? ? 16
>>>> # of expected failures ? ? ? ? ?54
>>>>
>>>> Cheers,
>>>> Kai
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> Thanks for also sending me the logs privately.
>>>
>>> It looks like the failures are related to printing long long types.
>>>
>>> Andrew - do you remember the origin of this addition to ffitest.h...
>>
>> Yes. ?See http://sourceware.org/ml/libffi-discuss/2009/msg00159.html
>>
>> Summary: mingw64 can't printf a long long. ?According
>> to Timothy Wall, "PRId64" is supposed to work on mingw64.
>>
>> Andrew.
>
> I don't think "PRId64" is supposed to be in quotes, since it's a macro, but
> I can't test atm.
Indeed, PRId64 is a macro and has not to be quoted, as otherwise it
simply gets a string, which isn't the intention here. Btw msvcrt can
display long long (default formatter here is for 32-bit and 64-bit
%I64[xoduX]). Just for the long double support you should define for
mingw either -D_POSIX=1 or -D__USE_MINGW_ANSI_STDIO=1 on command line
(or in source before any include as '#define __USE_MINGW_ANSI_STDIO
1'. By this macro internal printf routines are replaced by a POSIX
compatible implementation.
Regards,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination