#4132: [with new patch, needs a bit more work] complex arithmetic passes via 
pari
------------------------------+---------------------------------------------
 Reporter:  robertwb          |        Owner:  AlexGhitza
     Type:  enhancement       |       Status:  assigned  
 Priority:  major             |    Milestone:  sage-3.1.3
Component:  basic arithmetic  |   Resolution:            
 Keywords:                    |  
------------------------------+---------------------------------------------
Changes (by AlexGhitza):

  * summary:  [with patch, nearly positive review] complex arithmetic
              passes via pari => [with new patch, needs a bit
              more work] complex arithmetic passes via pari

Comment:

 Hi Robert,

 Thanks for looking at this so carefully!  I have uploaded an additional
 patch that gets rid of the long's and avoids computing cosh's as you
 suggested.  This does indeed speed things by about 1/4.  Having seen your
 other comment, can I leave it to you to make sqrt fast?  I tried the code
 you posted above and it is really fast, but I didn't look into stability
 questions.

 On a related note, I emailed Paul Zimmermann to ask if MPFR could get a
 function mpfr_sinh_cosh() sometime in the future.  Then I stumbled upon
 his library MPC (see http://www.multiprecision.org/mpc/ ).  Should we
 start thinking about using this as the backbone for arbitrary precision
 complex numbers, the same way we use MPFR for real numbers?

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4132#comment:11>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to