-Original Message-
From: Dongsheng Song
Sent: Tuesday, March 12, 2013 2:25 PM
To: gcc@gcc.gnu.org ; m...@loria.fr
Subject: [MPFR] Re: GNU MPFR 3.1.2 Release Candidate
Test on x86_64-w64-mingw32, only tfprintf.exe, tprintf.exe,
tsprintf.exe, and tstrtofr.exe FAILED, the other tests pa
On Mon, Mar 11, 2013 at 5:30 PM, Georg-Johann Lay wrote:
> Richard Biener wrote:
>> On Fri, Mar 8, 2013 at 5:03 PM, Georg-Johann Lay wrote:
>>> Richard Biener wrote:
On Fri, Mar 8, 2013 at 3:19 PM, Richard Biener
wrote:
> On Fri, Mar 8, 2013 at 2:57 PM, Georg-Johann Lay wrote:
I use stable/v2.x of mingw-w64, not trunk.
On Tue, Mar 12, 2013 at 4:43 PM, wrote:
>
>
> -Original Message- From: Dongsheng Song
> Sent: Tuesday, March 12, 2013 2:25 PM
> To: gcc@gcc.gnu.org ; m...@loria.fr
> Subject: [MPFR] Re: GNU MPFR 3.1.2 Release Candidate
>
>
>> Test on x86_64-w64-
You have in your test output:
Error in mpfr_vsprintf (s, "%.*Zi, %R*e, %Lf", ...);
expected: "0010610209857723, -1.2345678875e+07, 0.032258"
got: "0010610209857723, -1.2345678875e+07, 0.00"
That "0.00" for the "%Lf" usually indicates that the "%Lf" formatting is
not supporte
On Tue, Mar 12, 2013 at 6:54 PM, wrote:
> You have in your test output:
>
>
> Error in mpfr_vsprintf (s, "%.*Zi, %R*e, %Lf", ...);
> expected: "0010610209857723, -1.2345678875e+07, 0.032258"
> got: "0010610209857723, -1.2345678875e+07, 0.00"
>
> That "0.00" for the "%Lf" usua
Hi Dongsheng,
> > Is it the same for your compiler ?
>
> Yes.
then you should define __USE_MINGW_ANSI_STDIO as pointed out by Rob.
However it is strange that the configure did not detect that %Lf was not
supported. Please could you send the config.log and the output from configure?
Paul
Hi,
> Test on x86_64-w64-mingw32, only tfprintf.exe, tprintf.exe,
> tsprintf.exe, and tstrtofr.exe FAILED, the other tests passed.
>
> fixme:msvcrt:pf_printf_a multibyte characters printing not supported
> Error in test 8, got '% a. 15, b. -1, c. td'
> Error in test #8: mpfr_vfprintf print
On Tue, Mar 12, 2013 at 8:02 PM, Zimmermann Paul
wrote:
>Hi Dongsheng,
>
>> > Is it the same for your compiler ?
>>
>> Yes.
>
> then you should define __USE_MINGW_ANSI_STDIO as pointed out by Rob.
>
Perfect, now all tests passed !
> A quick grep shows not many targets would be affected, AVR, m32c, rl78 and
> spu.
> You should work with the maintainers of those targets to see which approach
> would be the best.
For both m32c and rl78, one address space is a strict subset of the
other (16-bit "near" vs 20/24/32-bit "far" po
Thanks for your informative response, David! This is what I really
wanted to know:
> All previous and current releases of GCC do not support
> native TLS on AIX. GCC 4.8 will provide TLS on AIX, as listed in the
> announcements for the release.
Great! I'll look forward to testing with 4.8 when it
On Tue, Mar 12, 2013 at 3:06 PM, Jason Vas Dias
wrote:
> But why didn't the compiler complain that TLS was not supported ?
> Shouldn't it be doing so ? It is definitely not OK in my book for gcc
> to finish compilation and linkage with no errors or warnings, when
> it has encountered a __thread
11 matches
Mail list logo
