DOCSLIB.ORG

Intel® Itanium™ Processor- Specific Application Binary Interface (ABI)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Intel® Itanium™ Processor- Specific Application Binary Interface (ABI) Intel® Itanium™ Processor- specific Application Binary Interface (ABI) May 2001 Document Number: 245370-003 Information in this document is provided in connection with Intel® products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The Itanium processor may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel’s website at http://developer.intel.com/design/litcentr. Itanium and i386 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other brands and names may be claimed as the property of others. Copyright © 2001, Intel Corporation. Contents 1 Introduction.......................................................................................................1-1 1.1 The Intel® Itanium™ Architecture and the System V ABI .....................1-1 1.2 How to Use the System V ABI for Intel® Itanium™ Processors............1-1 1.3 Evolution of the ABI Specification .........................................................1-2 1.4 Additional Documents ...........................................................................1-2 2 Software Installation.........................................................................................2-1 3 Low-level System Information.........................................................................3-1 3.1 Introduction............................................................................................3-1 3.2 Machine Interface..................................................................................3-1 3.2.1 Fundamental Types ..............................................................3-1 3.3 Operating System Interface...................................................................3-2 3.3.1 Exception Interface ...............................................................3-2 3.3.2 Signal Delivery ......................................................................3-3 3.3.3 Signal Handler Interface........................................................3-5 3.3.4 Debugging Support ...............................................................3-6 3.3.5 Process Startup.....................................................................3-6 4 Object Files .......................................................................................................4-1 4.1 ELF Header ...........................................................................................4-1 4.1.1 Machine Information..............................................................4-1 4.2 Sections.................................................................................................4-3 4.2.1 Section Types .......................................................................4-3 4.2.2 Section Attribute Flags ..........................................................4-4 4.2.3 Special Sections....................................................................4-4 4.2.4 Architecture Extensions ........................................................4-6 4.3 Relocations............................................................................................4-6 4.3.1 Relocation Types ..................................................................4-6 5 Program Loading and Dynamic Linking.........................................................5-1 5.1 Program Header....................................................................................5-1 5.2 Program Loading...................................................................................5-1 5.2.1 Linktime and Runtime Addresses .........................................5-4 5.2.2 Initializations..........................................................................5-4 5.3 Dynamic Linking ....................................................................................5-4 5.3.1 Dynamic Linker .....................................................................5-4 5.3.2 Dynamic Section ...................................................................5-5 5.3.3 Shared Object Dependencies ...............................................5-5 5.3.4 Global Offset Table ...............................................................5-6 5.3.5 Function Addresses ..............................................................5-6 5.3.6 Procedure Linkage Table ......................................................5-7 5.3.7 Initialization and Termination Functions..............................5-10 6 Libraries.............................................................................................................6-1 6.1 Unwind Library Interface .......................................................................6-1 6.1.1 Exception Handler Framework..............................................6-1 6.1.2 Data Structures .....................................................................6-3 Intel® Itanium™ Processor-specific Application Binary Interface (ABI) iii 6.1.3 Throwing an Exception .........................................................6-5 6.1.4 Exception Object Management.............................................6-7 6.1.5 Context Management............................................................6-7 6.1.6 Personality Routine...............................................................6-9 7 Miscellaneous ...................................................................................................7-1 7.1 Introduction ...........................................................................................7-1 7.2 Development Environment....................................................................7-1 7.2.1 Pre-defined Preprocessor Symbols ......................................7-1 7.2.2 Pre-defined Preprocessor Assertions ...................................7-1 7.2.3 Compiler Pragmas ................................................................7-2 7.3 ILP32 ABI ..............................................................................................7-3 7.3.1 Objectives of the 32-bit Little-endian Runtime Architecture ..7-3 7.3.2 Changes from the 64-bit Software Conventions ...................7-3 7.3.3 Addressing and Protection....................................................7-4 7.3.4 Data Allocation......................................................................7-4 7.3.5 Local Memory Stack Variables..............................................7-4 7.3.6 Parameter Passing ...............................................................7-4 7.4 Synchronization Primitives ....................................................................7-4 7.4.1 Atomic Fetch-and-op Operations ..........................................7-5 7.4.2 Atomic Op-and-fetch Operations...........................................7-6 7.4.3 Atomic Compare-and-swap Operation..................................7-6 7.4.4 Atomic Synchronize Operation..............................................7-6 7.4.5 Atomic Lock-test-and-set Operation......................................7-7 7.4.6 Atomic Lock_release Operation............................................7-7 7.5 Thread-Local Storage ...........................................................................7-7 7.5.1 C/C++ Programming Interface ..............................................7-7 7.5.2 Compile-time Allocation of Thread-Local Storage.................7-8 7.5.3 Linker Treatment of Thread-Local Storage Sections ............7-9 7.5.4 Runtime Allocation of Thread-Local Storage ......................7-10 7.5.5 Code Sequences for Accessing Thread-Local Variables....7-13 7.5.6 ELF Relocations for Thread-Local Storage.........................7-15 7.5.7 TLS Variable References....................................................7-15 Figures 3-1 Double-extended (80-bit) Floating-point Formats ..............................................3-2 4-1 Instruction Bundle Layout...................................................................................4-7 4-2 Relocatable Fields..............................................................................................4-8 5-1 Example Executable File....................................................................................5-2 5-2 Example Program Header Segments ................................................................5-2
Load more

Recommended publications
  • Nessus 8.3 User Guide
    Nessus 8.3.x User Guide Last Updated: September 24, 2021 Table of Contents Welcome to Nessus 8.3.x 12 Get Started with Nessus 15 Navigate Nessus 16 System Requirements 17 Hardware Requirements 18 Software Requirements 22 Customize SELinux Enforcing Mode Policies 25 Licensing Requirements 26 Deployment Considerations 27 Host-Based Firewalls 28 IPv6 Support 29 Virtual Machines 30 Antivirus Software 31 Security Warnings 32 Certificates and Certificate Authorities 33 Custom SSL Server Certificates 35 Create a New Server Certificate and CA Certificate 37 Upload a Custom Server Certificate and CA Certificate 39 Trust a Custom CA 41 Create SSL Client Certificates for Login 43 Nessus Manager Certificates and Nessus Agent 46 Install Nessus 48 Copyright © 2021 Tenable, Inc. All rights reserved. Tenable, Tenable.io, Tenable Network Security, Nessus, SecurityCenter, SecurityCenter Continuous View and Log Correlation Engine are registered trade- marks of Tenable,Inc. Tenable.sc, Tenable.ot, Lumin, Indegy, Assure, and The Cyber Exposure Company are trademarks of Tenable, Inc. All other products or services are trademarks of their respective Download Nessus 49 Install Nessus 51 Install Nessus on Linux 52 Install Nessus on Windows 54 Install Nessus on Mac OS X 56 Install Nessus Agents 58 Retrieve the Linking Key 59 Install a Nessus Agent on Linux 60 Install a Nessus Agent on Windows 64 Install a Nessus Agent on Mac OS X 70 Upgrade Nessus and Nessus Agents 74 Upgrade Nessus 75 Upgrade from Evaluation 76 Upgrade Nessus on Linux 77 Upgrade Nessus on Windows 78 Upgrade Nessus on Mac OS X 79 Upgrade a Nessus Agent 80 Configure Nessus 86 Install Nessus Home, Professional, or Manager 87 Link to Tenable.io 88 Link to Industrial Security 89 Link to Nessus Manager 90 Managed by Tenable.sc 92 Manage Activation Code 93 Copyright © 2021 Tenable, Inc.
    [Show full text]
  • I386-Engine™ Technical Manual
    i386-Engine™ C/C++ Programmable, 32-bit Microprocessor Module Based on the Intel386EX Technical Manual 1950 5 th Street, Davis, CA 95616, USA Tel: 530-758-0180 Fax: 530-758-0181 Email: [email protected] http://www.tern.com Internet Email: [email protected] http://www.tern.com COPYRIGHT i386-Engine, VE232, A-Engine, A-Core, C-Engine, V25-Engine, MotionC, BirdBox, PowerDrive, SensorWatch, Pc-Co, LittleDrive, MemCard, ACTF, and NT-Kit are trademarks of TERN, Inc. Intel386EX and Intel386SX are trademarks of Intel Coporation. Borland C/C++ are trademarks of Borland International. Microsoft, MS-DOS, Windows, and Windows 95 are trademarks of Microsoft Corporation. IBM is a trademark of International Business Machines Corporation. Version 2.00 October 28, 2010 No part of this document may be copied or reproduced in any form or by any means without the prior written consent of TERN, Inc. © 1998-2010 1950 5 th Street, Davis, CA 95616, USA Tel: 530-758-0180 Fax: 530-758-0181 Email: [email protected] http://www.tern.com Important Notice TERN is developing complex, high technology integration systems. These systems are integrated with software and hardware that are not 100% defect free. TERN products are not designed, intended, authorized, or warranted to be suitable for use in life-support applications, devices, or systems, or in other critical applications. TERN and the Buyer agree that TERN will not be liable for incidental or consequential damages arising from the use of TERN products. It is the Buyer's responsibility to protect life and property against incidental failure. TERN reserves the right to make changes and improvements to its products without providing notice.
    [Show full text]
  • DOS Virtualized in the Linux Kernel
    DOS Virtualized in the Linux Kernel Robert T. Johnson, III Abstract Due to the heavy dominance of Microsoft Windows® in the desktop market, some members of the software industry believe that new operating systems must be able to run Windows® applications to compete in the marketplace. However, running applications not native to the operating system generally causes their performance to degrade significantly. When the application and the operating system were written to run on the same machine architecture, all of the instructions in the application can still be directly executed under the new operating system. Some will only need to be interpreted differently to provide the required functionality. This paper investigates the feasibility and potential to speed up the performance of such applications by including the support needed to run them directly in the kernel. In order to avoid the impact to the kernel when these applications are not running, the needed support was built as a loadable kernel module. 1 Introduction New operating systems face significant challenges in gaining consumer acceptance in the desktop marketplace. One of the first realizations that must be made is that the majority of this market consists of non-technical users who are unlikely to either understand or have the desire to understand various technical details about why the new operating system is “better” than a competitor’s. This means that such details are extremely unlikely to sway a large amount of users towards the operating system by themselves. The incentive for a consumer to continue using their existing operating system or only upgrade to one that is backwards compatible is also very strong due to the importance of application software.
    [Show full text]
  • Enclave Security and Address-Based Side Channels
    Graz University of Technology Faculty of Computer Science Institute of Applied Information Processing and Communications IAIK Enclave Security and Address-based Side Channels Assessors: A PhD Thesis Presented to the Prof. Stefan Mangard Faculty of Computer Science in Prof. Thomas Eisenbarth Fulfillment of the Requirements for the PhD Degree by June 2020 Samuel Weiser Samuel Weiser Enclave Security and Address-based Side Channels DOCTORAL THESIS to achieve the university degree of Doctor of Technical Sciences; Dr. techn. submitted to Graz University of Technology Assessors Prof. Stefan Mangard Institute of Applied Information Processing and Communications Graz University of Technology Prof. Thomas Eisenbarth Institute for IT Security Universit¨atzu L¨ubeck Graz, June 2020 SSS AFFIDAVIT I declare that I have authored this thesis independently, that I have not used other than the declared sources/resources, and that I have explicitly indicated all material which has been quoted either literally or by content from the sources used. The text document uploaded to TUGRAZonline is identical to the present doctoral thesis. Date, Signature SSS Prologue Everyone has the right to life, liberty and security of person. Universal Declaration of Human Rights, Article 3 Our life turned digital, and so did we. Not long ago, the globalized commu- nication that we enjoy today on an everyday basis was the privilege of a few. Nowadays, artificial intelligence in the cloud, smartified handhelds, low-power Internet-of-Things gadgets, and self-maneuvering objects in the physical world are promising us unthinkable freedom in shaping our personal lives as well as society as a whole. Sadly, our collective excitement about the \new", the \better", the \more", the \instant", has overruled our sense of security and privacy.
    [Show full text]
  • MILITARY I386tm SX MICROPROCESSOR
    MILITARY i386TM SX MICROPROCESSOR Y Full 32-Bit Internal Architecture Y Virtual M8086 Mode Allows Execution Ð 8-, 16-, 32-Bit Data Types of M8086 Software in a Protected and Ð 8 General Purpose 32-Bit Registers Paged System Y Runs Intel386TM Software in a Cost Y High Speed Numerics Support with the Effective 16-Bit Hardware Environment Military i387TM SX Coprocessor Ð Runs Same Applications and O.S.'s Y On-Chip Debugging Support Including TM as the Military i386 DX Processor Breakpoint Registers Ð Object Code Compatible with M8086, M80186, M80286, and i386 Y Complete System Development Processors Support Ð Runs MS-DOS*, OS/2* and UNIX** Ð Software: C, PL/M, Assembler Ð Debuggers: PMON-i386 DX, Y Very High Performance 16-Bit Data Bus ICETM-i386 SX Ð 20 MHz Clock Ð Extensive Third-Party Support: C, Ð Two-Clock Bus Cycles Pascal, FORTRAN, BASIC, Ada*** on Ð 20 Megabytes/Sec Bus Bandwidth VAX, UNIX**, MS-DOS*, and Other Ð Address Pipelining Allows Use of Hosts Slower/Cheaper Memories Y High Speed CHMOS IV Technology Y Integrated Memory Management Unit Ð Virtual Memory Support Y 88-Lead Pin Grid Array Package Ð Optional On-Chip Paging (See Packaging Specification, Order Ý 231369) Ð 4 Levels of Hardware Enforced Y 100-Lead Plastic Flat Pack Package Protection Y Available in Four Product Grades: Ð MMU Fully Compatible with Those of Ð MIL-STD-883 (PGA), b55§Cto the M80286 and i386 DX CPUs a125§C(TC) Y Large Uniform Address Space Ð Military Temperature Only (PGA), Ð 16 Megabyte Physical b55§Ctoa125§C(TC) Ð 64 Terabyte Virtual Ð Extended Temperature (PGA), Ð 4 Gigabyte Maximum Segment Size b40§Ctoa110§C(TC) Ð Extended Temperature (PQFP), b20§Ctoa100§C(TC) The Military i386 SX Microprocessor is a 32-bit CPU with a 16-bit external data bus and a 24-bit external address bus.
    [Show full text]
  • Computer Architectures an Overview
    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
    [Show full text]
  • 5 Microprocessors
    Color profile: Disabled Composite Default screen BaseTech / Mike Meyers’ CompTIA A+ Guide to Managing and Troubleshooting PCs / Mike Meyers / 380-8 / Chapter 5 5 Microprocessors “MEGAHERTZ: This is a really, really big hertz.” —DAVE BARRY In this chapter, you will learn or all practical purposes, the terms microprocessor and central processing how to Funit (CPU) mean the same thing: it’s that big chip inside your computer ■ Identify the core components of a that many people often describe as the brain of the system. You know that CPU CPU makers name their microprocessors in a fashion similar to the automobile ■ Describe the relationship of CPUs and memory industry: CPU names get a make and a model, such as Intel Core i7 or AMD ■ Explain the varieties of modern Phenom II X4. But what’s happening inside the CPU to make it able to do the CPUs amazing things asked of it every time you step up to the keyboard? ■ Install and upgrade CPUs 124 P:\010Comp\BaseTech\380-8\ch05.vp Friday, December 18, 2009 4:59:24 PM Color profile: Disabled Composite Default screen BaseTech / Mike Meyers’ CompTIA A+ Guide to Managing and Troubleshooting PCs / Mike Meyers / 380-8 / Chapter 5 Historical/Conceptual ■ CPU Core Components Although the computer might seem to act quite intelligently, comparing the CPU to a human brain hugely overstates its capabilities. A CPU functions more like a very powerful calculator than like a brain—but, oh, what a cal- culator! Today’s CPUs add, subtract, multiply, divide, and move billions of numbers per second.
    [Show full text]
  • Opinion Ten Reasons Why HP’S Itanium-Based Servers Have Reached the Point-Of-No-Return
    Opinion Ten Reasons Why HP’s Itanium-based Servers Have Reached the Point-of-No-Return Executive Summary Hewlett-Packard (HP) refers to its HP Integrity and Integrity NonStop Itanium-based servers as “business critical systems”. In Q4, 2007, HP sold over $1 billion of these business critical systems. But, since then, due to a number of factors, Itanium-based server sales have declined significantly. Over the past year, business critical systems sales have hovered in the $400 million range per quarter, an almost 60% decline as compared with the 2007 high-mark. From our perspective, HP’s Itanium-based servers have now achieved a form of stasis (a medical term that refers to an inactive state). We expect a rise in Itanium business this quarter (due to pent-up demand for the new Itanium 9500), but we also expect that – within in a few quarters – underlying, dogging problems will again drive Itanium business downward. These problems include HP’s financial woes; increased competition (particularly from Intel x86-based servers); market factors (such as the market move toward Linux and a market preference for x86 architecture); a broken ecosystem (where HP has actually had to take legal action to get a business partner to keep supporting its independent software on Itanium-based platforms); an ill-founded Itanium recovery plan known as “converged infrastructure”; and more (in fact, we list a total of ten reasons why we believe HP’s Itanium-based servers have reached the point-of-no- return on page 2 of this Opinion)… In this Opinion , Clabby Analytics describes why we believe that HP’s business critical Integrity servers have now reached the point-of-no-return.
    [Show full text]
  • The IA-32 Processor Architecture
    The IA-32 processor architecture Nicholas FitzRoy-Dale Document Revision: 1 Date: 2006/05/30 22:31:24 [email protected] http://www.cse.unsw.edu.au/∼disy/ Operating Systems and Distributed Systems Group School of Computer Science and Engineering The University of New South Wales UNSW Sydney 2052, Australia 1 Introduction This report discusses the most common instruction set architecture for desktop microprocessors: IA- 32. From a programmer’s perspective, IA-32 has not changed changed significantly since its introduc- tion with the Intel 80386 processor in 1985. IA-32 implementations, however, have undergone dra- matic changes in order to stay competitive with more modern architectures, particularly in the area of instruction-level parallelism. This report discusses the history of IA-32, and then the architectural features of recent IA-32 im- plementations, with particular regard to caching, multiprocessing, and instruction-level parallelism. An archtectural description is not particularly useful in isolation. Therefore, to provide context, each as- pect is compared with analogous features of other architectures, with particular attention paid to the RISC-style ARM processor and the VLIW-inspired Itanium. 2 A brief history of IA-32 IA-32 first appeared with the 80386 processor, but the architecture was by no means completely new. IA-32’s 8-bit predecessor first appeared in the Datapoint 2200 programmable terminal, released in 1971. Under contract to produce a single-chip version of the terminal’s multiple-chip TTL design, Intel’s im- plementation, the 8008, was not included in the terminal. Intel released the chip in 1972.
    [Show full text]
  • Intel Itanium 2 Processors Get Faster Bus Architecture 18 July 2005
    Intel Itanium 2 Processors Get Faster Bus Architecture 18 July 2005 Intel Corporation today introduced two Intel Itanium based servers. 2 processors which deliver better performance over the current generation for database, business The improved front side bus bandwidth allows for intelligence, enterprise resource planning and 10.6 gigabits of data per second to pass from the technical computing applications. processor to other system components. In contrast, the current generation 400 MHz FSB transfers 6.4 For the first time, Itanium 2 processors have a 667 gigabits of data per second. The ability to move megahertz (MHz) front side bus (FSB), which more data in a very short period of time is critical to connects and transfers data between the compute intensive applications in the scientific, oil microprocessor, chipset and system's main and gas and government industries. memory. Servers designed to utilize the new bus are expected to deliver more than 65 percent Hitachi, which will adopt the new Itanium 2 greater system bandwidth over servers designed processors with the 667 FSB into new Hitachi with current Itanium 2 processors with a 400 MHz BladeSymphony* servers coming in the next 30 FSB. This new capability will help set the stage for days, has also designed a chipset (the the forthcoming dual core Itanium processor, communications controller between the processor codenamed "Montecito," which will feature the and the rest of the computer system) to take same bus architecture. advantage of the new bus architecture. "Intel continues to bring new capabilities to the Platforms using Montecito are expected to deliver Itanium architecture, evolving the platform to up to twice the performance, up to three times the further improve performance for data intensive system bandwidth, and more than 2 1/2 times as tasks," said Kirk Skaugen, general manager of much on-die cache as the current generation of Intel's Server Platforms Group.
    [Show full text]
  • Hardware-Enabled Security: 3 Enabling a Layered Approach to Platform Security for Cloud 4 and Edge Computing Use Cases
    1 Draft NISTIR 8320 2 Hardware-Enabled Security: 3 Enabling a Layered Approach to Platform Security for Cloud 4 and Edge Computing Use Cases 5 6 Michael Bartock 7 Murugiah Souppaya 8 Ryan Savino 9 Tim Knoll 10 Uttam Shetty 11 Mourad Cherfaoui 12 Raghu Yeluri 13 Akash Malhotra 14 Karen Scarfone 15 16 17 18 This publication is available free of charge from: 19 https://doi.org/10.6028/NIST.IR.8320-draft 20 21 22 23 Draft NISTIR 8320 24 Hardware-Enabled Security: 25 Enabling a Layered Approach to Platform Security for Cloud 26 and Edge Computing Use Cases 27 Michael Bartock 28 Murugiah Souppaya 29 Computer Security Division 30 Information Technology Laboratory 31 32 Ryan Savino 33 Tim Knoll 34 Uttam Shetty 35 Mourad Cherfaoui 36 Raghu Yeluri 37 Intel Data Platforms Group 38 Santa Clara, CA 39 40 Akash Malhotra 41 AMD Product Security and Strategy Group 42 Austin, TX 43 44 Karen Scarfone 45 Scarfone Cybersecurity 46 Clifton, VA 47 48 49 50 May 2021 51 52 53 54 U.S. Department of Commerce 55 Gina Raimondo, Secretary 56 57 National Institute of Standards and Technology 58 James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce 59 for Standards and Technology & Director, National Institute of Standards and Technology 60 National Institute of Standards and Technology Interagency or Internal Report 8320 61 58 pages (May 2021) 62 This publication is available free of charge from: 63 https://doi.org/10.6028/NIST.IR.8320-draft 64 Certain commercial entities, equipment, or materials may be identified in this document in order to describe an 65 experimental procedure or concept adequately.
    [Show full text]
  • Intel® Itanium™ Processor Microarchitecture Overview
    Itanium™ Processor Microarchitecture Overview Intel® Itanium™ Processor Microarchitecture Overview Harsh Sharangpani Principal Engineer and IA-64 Microarchitecture Manager Intel Corporation ® Microprocessor Forum October 5-6, 1999 Itanium™ Processor Microarchitecture Overview Unveiling the Intel® Itanium™ Processor Design l Leading-edge implementation of IA-64 architecture for world-class performance l New capabilities for systems that fuel the Internet Economy l Strong progress on initial silicon ® Microprocessor Forum 2 October 5-6, 1999 Itanium™ Processor Microarchitecture Overview Itanium™ Processor Goals l World-class performance on high-end applications – High performance for commercial servers – Supercomputer-level floating point for technical workstations l Large memory management with 64-bit addressing l Robust support for mission critical environments – Enhanced error correction, detection & containment l Full IA-32 instruction set compatibility in hardware l Deliver across a broad range of industry requirements – Flexible for a variety of OEM designs and operating systems Deliver world-class performance and features for servers & workstations and emerging internet applications ® Microprocessor Forum 3 October 5-6, 1999 Itanium™ Processor Microarchitecture Overview EPIC Design Philosophy ì Maximize performance via EPICEPIC hardware & software synergy ì Advanced features enhance instruction level parallelism ìPredication, Speculation, ... ì Massive hardware resources for parallel execution VLIW OOO / SuperScalar ì High performance
    [Show full text]