[NumPy-Tickets] [NumPy] #1633: Changeset 8438 breaks ldexp on 64bit/bigendian systems

NumPy Trac numpy-tickets@scipy....
Mon Oct 11 16:44:50 CDT 2010


#1633: Changeset 8438 breaks ldexp on 64bit/bigendian systems
--------------------+-------------------------------------------------------
 Reporter:  nics    |       Owner:  somebody    
     Type:  defect  |      Status:  needs_review
 Priority:  normal  |   Milestone:  1.5.1       
Component:  Other   |     Version:  1.5.0       
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by nics):

 > I'm not saying that it should be left as it is now
 Sorry, i didn't want to be crude. It just sounded to be as if you wanted
 to change the ldexp_signatures back to using PyArray_LONG and introducing
 some crazy pointer magic ;)

 Why is using numpy a long as default, not an int? There are reasons for
 why the int's are what they are on every platform, I guess (efficiency,
 storage size, application of SIMDs, ...).
 But now, being faced with the reality: What about introducing a cast from
 np.int to np.intc that possibly throws on overflow?

-- 
Ticket URL: <http://projects.scipy.org/numpy/ticket/1633#comment:6>
NumPy <http://projects.scipy.org/numpy>
My example project


More information about the NumPy-Tickets mailing list