Post Reply 
linsolve bug
08-26-2023, 02:57 PM
Post: #8
RE: linsolve bug
FYI, this is result of time(linsolve(a,b)). Timing 2nd digit is just a rough guess.

Code:
XCas-1.5.0:         TIME
    53 bits double  6.0E-5
    16 digits MPFR  2.8E-4
    32 digits MPFR  3.2E-4
    
XCas-1.9.0:
    48 bits trunc   6.2E-6
    16 digits MPFR  1.2E-4
    32 digits MPFR  1.3E-4

MPFR timings are basically the same, regardless of setting digits to 16 or 32, or even 100.

Order of magnitude difference between 48 bits and IEEE double is odd.
Perhaps comparing wildly different XCas versions is not a good idea.
But, that's the only 2 versions I had to test.

Anyone has XCas 1.90 (win32), compiled with the -DDOUBLEVAL flag ?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
linsolve bug - Albert Chan - 08-24-2023, 01:57 PM
RE: linsolve bug - parisse - 08-24-2023, 02:24 PM
RE: linsolve bug - Albert Chan - 08-24-2023, 04:12 PM
RE: linsolve bug - Albert Chan - 08-28-2023, 01:03 PM
RE: linsolve bug - parisse - 08-25-2023, 03:19 PM
RE: linsolve bug - Albert Chan - 08-25-2023, 04:34 PM
RE: linsolve bug - parisse - 08-25-2023, 06:58 PM
RE: linsolve bug - Albert Chan - 08-26-2023 02:57 PM
RE: linsolve bug - Albert Chan - 08-25-2023, 08:24 PM
RE: linsolve bug - parisse - 08-27-2023, 06:47 AM
RE: linsolve bug - Albert Chan - 08-27-2023, 09:15 AM



User(s) browsing this thread: 2 Guest(s)