-fPIC is on by default on Mac OS X, so that's easy. Having 64-bit floats is quite nice on the interface side because it means you can have large integers in Pd, like timestamps.
.hc
On Dec 16, 2006, at 1:24 AM, glauber alex dias prado wrote:
Except for some problems compiling some externals like osc that needs a fPIC i guess that Pd works ok, i am running linux64 a gentoo system and tcl/tk is working.
Em Sex, 2006-12-15 às 17:34 -0500, Hans-Christoph Steiner escreveu:
Does anyone know anything about the 64-bit support in Tcl/Tk? I was thinking of making 64-bit native G5 and Xeon builds of Pd, once everything is release.
That said, does the "--enable-threads" thing do anything for us?
.hc
All information should be free. - the hacker ethic
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
On 12/16/06, Hans-Christoph Steiner hans@eds.org wrote:
-fPIC is on by default on Mac OS X, so that's easy. Having 64-bit floats is quite nice on the interface side because it means you can have large integers in Pd, like timestamps.
The 64 bit buzzword refers to memory addressing; double precision floats are different than 64 bit CPUs or applications. FPUs have used 64 bit floats for years regardless of their addressing capabilities.
On Dec 16, 2006, at 12:18 PM, chris clepper wrote:
On 12/16/06, Hans-Christoph Steiner hans@eds.org wrote:
-fPIC is on by default on Mac OS X, so that's easy. Having 64-bit floats is quite nice on the interface side because it means you can have large integers in Pd, like timestamps.
The 64 bit buzzword refers to memory addressing; double precision floats are different than 64 bit CPUs or applications. FPUs have used 64 bit floats for years regardless of their addressing capabilities.
So does that mean it would be possible to make Pd use 64-bit floats on all CPUs without a major performance hit?
.hc
------------------------------------------------------------------------
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
On Sat, 16 Dec 2006, Hans-Christoph Steiner wrote:
On Dec 16, 2006, at 12:18 PM, chris clepper wrote:
The 64 bit buzzword refers to memory addressing; double precision floats are different than 64 bit CPUs or applications. FPUs have used 64 bit floats for years regardless of their addressing capabilities.
So does that mean it would be possible to make Pd use 64-bit floats on all CPUs without a major performance hit?
No, it's only possible to use 32-bit floats because the t_atom structure contains a t_word union, which is often assumed to be the same size as a C pointer; so in 32-bit mode you can only put a 32-bit float in a t_word.
If you put a double in t_word, then it becomes 8 bytes, so a t_atom depends 12 or 16 bytes depending on whether t_atomtype gets extended to the same size as the t_word. If it's 12 bytes you may get a slowdown due to non-alignment, and in both cases you have a slowdown because it's more RAM.
If t_atom were an opaque type, I know how to make it support 63-bit floats, as well as all the other possible atoms, all in a 8-byte (64-bit) structure, in both 32-bit and 64-bit mode. Note that I really mean 63-bit floats here, and not 64-bit. (The same trick could be applied to shrinking t_atom to 4 bytes in 32-bit mode if using 31-bit floats.)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada