Updating version number at compile time

During this time, HP had begun to believe that it was no longer cost-effective for individual enterprise systems companies such as itself to develop proprietary microprocessors.Intel had also been researching several architectural options for going beyond the x86 ISA to address high end enterprise server and high performance computing (HPC) requirements.This contrasts with other superscalar architectures, which depend on the processor to manage instruction dependencies at runtime.

Tukwila also implements Intel Quick Path Interconnect (QPI) to replace the Itanium bus-based architecture.

Thus Intel and HP partnered in 1994 to develop the IA-64 ISA, using a variation of VLIW design concepts which Intel named explicitly parallel instruction computing (EPIC).

Intel's goal was to leverage the expertise HP had developed in their early VLIW work along with their own to develop a volume product line targeted at high-end enterprise class servers and high performance computing (HPC) systems that could be sold to all original equipment manufacturers (OEMs) while HP wished to be able to purchase off-the-shelf processors that built using Intel's volume manufacturing and leading edge process technology that were higher performance and more cost effective than their current PA-RISC processors.

In order to establish what was their first new ISA in 20 years and bring an entirely new product line to market, Intel made a massive investment in product definition, design, software development tools, OS, software industry partnerships, and marketing.

To support this effort Intel created the largest design team in their history and a new marketing and industry enabling team completely separate from x86.

updating version number at compile time-56updating version number at compile time-81updating version number at compile time-84

Join our conversation (6 Comments).
Click Here To Leave Your Comment Updating version number at compile time.

Comments:

Leave a Reply

Your email address will not be published. Required fields are marked *