Jump to content

Talk:Floating-point unit

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by PeterJeremy (talk | contribs) at 21:23, 19 February 2010 (illegal to export: Unlikely to be affected by CoCom). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Old text moved from Talk:FPU

I do not think that Floating Point Units deal with Trigometric functions. Such functions are usually in a software library and use geometric series for evaluation. The evaluaton may be done using an FPU. Some FPU's implement square root I think! User:Rjstott

Some FPUs do trigonometric functions. For example, the 80387 has FSIN, FCOS, FSINCOS, FPTAN and FPATAN instructions. --Zundark, 2002 Jan 30
You are right about using series for evaluation and the square root but the 68881/68882 FPU, for instance, designed for the 68xxxx family of processors, include cos, sin, atan in microcode. When the FPU functions were integrated in the 68040, trigonometric functions were emulated, though. OprgaG

Unsorted text

when was it invented and by whom?

---

Why was this page deleted? There's no talk history discussing it and it doesn't show up in the deletion log. It does need some cleanup, but I'm just going to restore it. Nkedel 00:54, 6 March 2006 (UTC)[reply]

Should the second section be merged with coprocessor? Nkedel 02:03, 6 March 2006 (UTC)[reply]

---

The section on coprocessors is unnecessarily biased towards the x86. Many other chips until the early-mid 90s had separate coprocessors, even if they were not explicitly mentioned in the literature. MIPS comes to mind, but this was also true of the VAX and if memory serves HPPA. I can rewrite if necessary, but ideally someone with more specific knowledge than me would be better suited.

Examples of implementing SIMD using the FPU

The current comment that AMD64 is an example of a CPU architecture that uses the FPU to implement SIMD is technically correct, but may give an impression that this is only recently done. At the risk of being x86-centric, the example should any processors that implemented MMX or 3Dnow!, which dates back to the Pentium-MMX and K6. Calyth 06:51, 8 September 2006 (UTC)[reply]

illegal to export

There was a story (urban legend?) floating around my programming class, to the effect of: ... exporting floating point chips to certain countries was illegal and violates the terms of the CoCom ... CPU manufacturers specifically decided not to integrate FPUs on the CPU chip, but instead have separate CPU chips (that they could sell to those countries) and FPU chips ... after the law changed, making it legal to sell FPUs to those countries, CPU manufacturers immediately stopped making separate FPU chips and immediately began making integrated CPU+FPU chips. ...

Any truth to this story? If so, please mention the facts in the article. --68.0.124.33 (talk) 04:23, 13 April 2008 (UTC)[reply]

It seems unlikely. A more reasonable explanation is that changes in transistor count limits made it practical to include FPUs on-chip and the performance enhancements that this would provide make it attractive to do so.

--PeterJeremy (talk) 21:23, 19 February 2010 (UTC)[reply]

x86 Floating Point Processor

How about writing about how much the x86's floating point processor sucks in terms of accuracy? 141.225.144.225 (talk) 21:35, 24 May 2008 (UTC)[reply]

I think that the x87 uses 80-bit FPU registers to store 64-bit floating point values in extended precision. Anyways, it is IEEE compliant, so there is no reason to believe that it is "inaccurate". All FPUs are inaccurate to some extent, limited by the width of their registers. You were not referring to the Pentium FDIV bug were you? That only existed in the original Pentium and was due to a hardware bug, not the design. Anyways, such statements (that x87 sucks) is not suitable for Wikipedia (violates neutrality). Rilak (talk) 04:59, 25 May 2008 (UTC)[reply]