Le 27/01/2012 16:52, Willem Jan Palenstijn a écrit :
On Fri, Jan 27, 2012 at 02:05:25PM +0100, Julien Puydt wrote:
Le 26/01/2012 10:53, Dima Pasechnik a écrit :
Is the popcount() there even big-endian/little-endian safe?
It's not obvious. As well, it will blow on architectures that have
a different from x86 idea about the length of int...
So one quick test would be to use __builtin_popcount(i) and see if it
makes a difference...
I stupidly ran "rm -rf sage-4.8" in the terminal which pointed to
sage-4.8 full install thinking it was the terminal which pointed to
sage-4.8 spkg sources, so I had to rebuild from scratch. Sigh.
Anyway, I finally have sage-4.8 again on that box, and the result of
using the builtin popcount is that it still doesn't work.
Where do we go from that point on?
Is char signed or unsigned on your platform?
Good question ; how do I find out?
If unsigned, vertex_separation.pyx will have some problems.
Why?
Does the compiler show any warnings when compiling this file, by the way?
None.
Snark on #sagemath
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
