Thanks!
I can work with this, though I'd like to start merging after the next
release branch on January 7.
Much of the cut-and-paste is difficult to abstract over, but I worry
about the amount of cut-and-paste in the JIT. The inlined arithmetic
functions, like scheme_generate_arith(), seem like t
On 12/22/2012 10:24 AM, Michael Filonenko wrote:
Also, long double arithmetic requires setting "extended mode" flag on
FPU, which forces the FPU to use 80-bit registers. The side effect on
that flag is that the FPU gives slightly different (more accurate, but
not IEEE-compliant) results for 64-bi
Could you formulate some test cases to check for this behavior?
Robby
On Sun, Dec 23, 2012 at 7:07 PM, Neil Toronto wrote:
> On 12/22/2012 10:24 AM, Michael Filonenko wrote:
>
>> Also, long double arithmetic requires setting "extended mode" flag on
>> FPU, which forces the FPU to use 80-bit reg
I'm working on those now. There are some well-known
double-rounding-error cases I can use, and I've found more test cases by
randomized testing using bigfloats.
I wanted to avoid exact floating-point tests, but it seems there's no
way around it now. I hope DrDr's FPU is IEEE-compliant. We'll f
4 matches
Mail list logo
