[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUB and mpfr/mpc
From: |
Dan Eble |
Subject: |
Re: GUB and mpfr/mpc |
Date: |
Mon, 8 Dec 2014 20:41:08 -0500 |
> On Dec 8, 2014, at 08:21 , David Kastrup <address@hidden> wrote:
>
> Masamichi HOSODA <address@hidden> writes:
>
>>> I agree that changing the algorithms is preferred; I didn’t mean to
>> suggest otherwise. But if that’s not going to happen overnight, and
>> there is a way to mitigate the problem in the meantime without
>> touching the code, the people affected would value it.
>>
>> I tried "-mfpmath=sse -msse2".
>> It worked fine. bad_alloc didn't occur.
>> Correct PDF was generated.
>>
>> It can be a workaround until changing the algorithms.
>
> It's not architecture independent. And may blow up for other reasons.
But it’s good to know that the problem was floating point and not memory
corruption, so thanks for testing it.
—
Dan
- Re: GUB and mpfr/mpc, (continued)
- Re: GUB and mpfr/mpc, Masamichi HOSODA, 2014/12/04
- Re: GUB and mpfr/mpc, Masamichi HOSODA, 2014/12/04
- Re: GUB and mpfr/mpc, Dan Eble, 2014/12/04
- Re: GUB and mpfr/mpc, Masamichi HOSODA, 2014/12/05
- Re: GUB and mpfr/mpc, David Kastrup, 2014/12/05
- Re: GUB and mpfr/mpc, Dan Eble, 2014/12/05
- Re: GUB and mpfr/mpc, David Kastrup, 2014/12/06
- Re: GUB and mpfr/mpc, Dan Eble, 2014/12/06
- Re: GUB and mpfr/mpc, Masamichi HOSODA, 2014/12/08
- Re: GUB and mpfr/mpc, David Kastrup, 2014/12/08
- Re: GUB and mpfr/mpc,
Dan Eble <=
- Re: GUB and mpfr/mpc, Keith OHara, 2014/12/21
Re: GUB and mpfr/mpc, Masamichi Hosoda, 2014/12/28