Asserting that Itanium sets a new standard for floating-point mathematics, the authors assert that "a 64-bit wide number that an Itanium-based system can handle obviously holds many more levels of precision than a 32-bit number used by RISC machines." Perhaps thats why 80-bit floating-point registers have been used for two decades, for example in Intels own 8087 co-processor that many AutoCAD users plugged into their first-generation IBM PCs. There is a core proposition that distinguishes the Itanium from its competitors and its predecessors. Intel has gambled that the best way to get ahead of the complexity of on-chip instruction-scheduling hardware, which seeks out opportunities for parallelism on the fly, is to find those opportunities when a program is compiled and place parallelism in the code ahead of time: hence the Intel moniker EPIC, for "explicitly parallel instruction computing," that defines the genuine difference between Itanium and what has come before.Publishers warn aspiring authors that a book has to be thick enough for its spine to display a title that can be seen by prospective buyers as they scan a bookstores shelves. Itanium Rising shows the symptoms of a worthwhile vendor white paper being bulked up to 198-page book length, including 26 pages of prefatory material, definitions of terms, and index. My recommendation: if you want an Itanium sales pitch, dont buy a $30 book; let a sales rep buy you a $30 lunch that youre sure to find more substantial.
Title: Itanium Rising: Breaking Through Moores Second Law of Computing Power
Authors: Jim Carlson, Jerry Huck
Length: 204 pages
In asserting EPICs advantages, though, the authors over-reach. They spend all of Chapter 4 telling us that Itanium is needed to meet the demands of "utility computing" as a service delivered through heterogeneous, highly distributed systems. But they tell us in Chapter 15 that Itaniums advantage over other architectures comes from the EPIC compilers ability to "make global optimizations" as it runs through the entire stream of code that performs a task. When the code that performs a high-level task is residing on many different systems and created and maintained by many different parties, however, any advantage based on global analysis seems suspect; the pre-Itanium alternative of seeking parallelism opportunities on the fly seems intuitively more likely to pay off in such an environment.