History lesson, The correct term to use is really "floating point register". But the idea of a "float" that is being tossed in this discussion is really a "float variable".
This is what Graydon is talking about I pretty sure: http://www.gnu.org/software/gsl/manual/html_node/Examining-floating-point-registers.html There is a difference in terminology depending on WHAT you are really talking about, but it appears that Graydon "rocks it old school", as we all should when discussing the "register" capabilities themselves of the hardware (in years past an FPU... in current architectures a SIMD "capable" processor.) Besides all these terms are in the IEEE standards anyways http://en.wikipedia.org/wiki/IEEE_floating-point_standard (class dismissed) ;-) On Tue, Jul 2, 2013 at 1:07 AM, Daniel Micay <[email protected]> wrote: > On Tue, Jul 2, 2013 at 1:09 AM, Robert O'Callahan <[email protected]> > wrote: > > Seems to me you could quantify the performance impact of variable-width > > types. E.g. try making 'int' 32-bit on a 64-bit architecture and see how > > much it hurts. I'm suspicious they're a premature optimization. > > > > Rob > > The int and uint types match the pointer size, and if they aren't the > same size the existing standard library (including things like > vectors) won't work. > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > -- -Thad Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry> Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
