Design Issues in Floating-Point Division

Total Page:16

File Type:pdf, Size:1020Kb

Design Issues in Floating-Point Division DESIGN ISSUES IN FLOATING-POINT DIVISION Stuart F. Ob erman and Michael J. Flynn Technical Rep ort: CSL-TR-94-647 Decemb er 1994 This work was supp orted by NSF under contract MIP93-13701. DESIGN ISSUES IN FLOATING-POINT DIVISION by Stuart F. Ob erman and Michael J. Flynn Technical Rep ort: CSL-TR-94-647 Decemb er 1994 Computer Systems Lab oratory Departments of Electrical Engineering and Computer Science Stanford University Stanford, California 94305-4055 Abstract Floating-p oint division is generally regarded as a low frequency, high latency op eration in typical oating-p oint applications. However, the increasing emphasis on high p erformance graphics and the industry-wide usage of p erformance b enchmarks, such as SPECmarks, forces pro cessor designers to pay close attention to all asp ects of oating-p oint computation. This pap er presents the algorithms often utilized for oating-p oint division, and it also presents implementation alternatives available for designers. Using a system level study as a basis, it is shown howtypical oating-p oint applications can guide the designer in making implementation decisions and trade-o s. Key Words and Phrases: Floating-p oint, division, b enchmarks, system p erformance c Copyright 1994 by Stuart F. Ob erman and Michael J. Flynn Contents 1 Intro duction 1 2 Divide Algorithms: General Discussion 2 2.1 Subtractive Algorithms :: ::: :: ::: ::: ::: ::: ::: :: ::: :: 2 2.2 Multiplicative Algorithms : ::: :: ::: ::: ::: ::: ::: :: ::: :: 3 2.3 Comparison ::: ::: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 5 3 System Level Study 5 3.1 Instrumentation : ::: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 5 3.2 Metho d of Analysis :: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 6 4 Results 6 4.1 Instruction Mix : ::: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 6 4.2 Compiler E ects ::: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 6 4.3 Overall CPI ::: ::: ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 9 4.4 Shared Multiplier E ects :: ::: :: ::: ::: ::: ::: ::: :: ::: :: 10 4.5 On-the- y Rounding and Conversion ::: ::: ::: ::: ::: :: ::: :: 12 4.6 Consumers of Divide Results :: :: ::: ::: ::: ::: ::: :: ::: :: 13 5 Conclusion 15 6 Acknowledgement 15 iii List of Figures 1 Basic SRTTop ology : ::: ::: :: ::: ::: ::: ::: ::: :: ::: :: 4 2 Instruction count distribution :: :: ::: ::: ::: ::: ::: :: ::: :: 7 3 Functional unit stall time distribution :: ::: ::: ::: ::: :: ::: :: 7 4 Spice with optimization O0 ::: :: ::: ::: ::: ::: ::: :: ::: :: 8 5 Spice with optimization O3 ::: :: ::: ::: ::: ::: ::: :: ::: :: 8 6 Cumulativeaverage interlo ck distance :: ::: ::: ::: ::: :: ::: :: 9 7 Average e ective divide latency : :: ::: ::: ::: ::: ::: :: ::: :: 9 8 CPI and area vs divide latency : :: ::: ::: ::: ::: ::: :: ::: :: 11 9 CPI and area vs divide latency : :: ::: ::: ::: ::: ::: :: ::: :: 11 10 Excess CPI due to shared multiplier ::: ::: ::: ::: ::: :: ::: :: 12 11 E ects of on-the- y rounding and conversion : ::: ::: ::: :: ::: :: 13 12 Consumers of divide results ::: :: ::: ::: ::: ::: ::: :: ::: :: 14 13 Consumers of multiply results :: :: ::: ::: ::: ::: ::: :: ::: :: 14 iv List of Tables 1 E ects of compiler optimization : :: ::: ::: ::: ::: ::: :: ::: :: 10 v 1 Intro duction Mo dern computer applications have increased in their computation complexity in recent years. The development of high sp eed oating-p oint FP arithmetic is a requirementto meet the computation demands of mo dern applications whichhave increased in their com- putation complexity in recentyears. The emphasis on high p erformance graphics rendering systems has placed further demands on the computation abilities of pro cessors. Further- more, the industry-wide usage of p erformance b enchmarks, such as SPECmarks, forces pro cessor designers to pay particular attention to oating-p oint computation. Applications such as the aforementioned comprise several oating p oint op erations, among them addition, multiplication, and division. In recent FPUs, emphasis has b een placed on designing ever-faster adders and multipliers, with division receiving less attention. Typically, the range for addition latency is 2 to 4 cycles, and the range for multiplication is 2 to 8 cycles. In contrast, the latency for double precision division in mo dern FPUs ranges from 7 to 61 cycles [4]. This phenomenon is largely due to the p erception that divide is an infrequent op eration in mo dern oating-p oint applications. Because of the low frequency, it is b elieved that the overall p erformance degradation incurred by the use of a slow divider will not b e large. More emphasis has b een placed on improving the p erformance of addition and multiplication. As the p erformance gap widened b etween these two op erations and division, oating-p oint algorithms and applications have b een slowly rewritten to account for this gap by mitigating the use of divide. Thus, current applications and b enchmarks are usually written assuming that divide is an inherently slow op eration and should therefore b e used sparingly. While the metho dology for designing ecient high-p erformance adders and multipliers is well-understo o d, the design of dividers still remains a serious design challenge, often viewed as a \black-art" among system designers. Extensive theory exists describing the theory of division. However, the implementation of division has received less attention, and very little emphasis has b een placed on studying the e ects of FP division on overall system p erformance. This study investigates in more detail the relationship b etween FP divide and system p erformance. This relationship is studied in the context of a set of oating-p oint appli- cations. The choice of applications to use when studying the p erformance of a system is often dicult and controversial. The application suites considered for this study included the NAS Parallel Benchmarks [5], the Perfect Benchmarks [8], and the SPECfp92 [10] b enchmark suite. An initial analysis of the instruction distribution showed that the SPEC b enchmarks had the highest frequency of oating-p oint op erations, and they were therefore chosen as the target workload of the study to b est re ect the b ehavior of oating-p oint intensive applications. These applications are used to investigate several questions regarding the implementa- tion of oating-p oint division: Do es a high-latency divide op eration cause enough system p erformance degradation to warrant a separate, lower latency divide functional unit? Howwell can a compiler schedule co de in order to maximize the distance b etween 1 divide result pro duction and consumption? What are the e ects of increasing the width of instruction issue on e ective divide latency? If a hardware divide unit is warranted, should the divider share the FP multiplier hardware, or should it have its own dedicated functional unit? Is on-the- y rounding and conversion necessary? The remainder of this pap er is organized as follows. Section 2 presents common division algorithms and implementations. Section 3 describ es the metho d of obtaining data from the b enchmarks. Section 4 presents and analyzes the results of the study. Section 5 is the conclusion. 2 Divide Algorithms: General Discussion Many classes of algorithms exist for implementing division. These include the subtractive metho d, the multiplicative metho d, various approximation metho ds, and sp ecial metho ds such as the CORDIC and continued pro duct metho ds [1]. The most commonly used algo- rithms in mo dern FPUs are the subtractive and multiplicative metho ds, and the analysis here is limited to these. 2.1 Subtractive Algorithms Digit recurrence algorithms use subtraction as the iterative op erator. The quotient is rep- resented in a radix-r form and one digit of it is calculated in every iteration. This class b e can b e further divided into r estor ing and nonr estor ing division. Restoring division is similar to the familiar pap er and p encil division. When dividing two n-bit numb ers, the division can require up to 2n + 1 adds. The Winograd b ound [13] on restoring division in gate delays is therefore: T =2n+ 1 log 2n 2 Nonrestoring division eliminates the restoration cycles. Accordingly, the b ound on non- restoring division is given by: T = n log 2n 2 SRT is a nonrestoring division algorithm that is basically a trial and error pro cess [11]. It utilizes the following relationship: P = rP q D j +1 j j +1 To calculate a next partial remainder, the divisor is multiplied by the next quotient digit, and the result is subtracted from the pro duct of the last partial remainder, or dividend for the rst iteration, and a radix r. The next quotient digit is obtained by supplying a xed numb er of bits from the last partial remainder, approximately 8 bits for a radix-4 divider, 2 to a lo ok-up table. By cho osing a radix to b e a p ower of 2, the pro duct of the radix and the last partial remainder can b e formed by shifting. Similarly, the various pro ducts of the divisor multiplied by the next quotient digit can b e formed bymultiplexing di erent multiples of the divisor. However, the problem with this basic scheme is that it requires a full-width subtractor. Consequently, this scheme can b e very slow. In order to improve up on this basic scheme, some redundancy is often intro duced into the algorithm. An extra constraint is added to provide redundancy: jP j <kD j +1 where k = n / r - 1 and n is the numb er of p ositive allowed digits for the next quotient digit. A design tradeo can b e noted in this relationship. By using a large numb er of allowed digits for the next quotient digit, and thus a large value for k, a smaller lo ok-up table is required, and thus the complexity and latency of the table lo ok-up can b e reduced. However, cho osing a smaller numb er of allowed digits for the quotient simpli es the generation of the multiple of the divisor. Multiples that are p owers of two can b e formed by simply shifting. If a multiple is required that is not a p ower of two e.g. three, an additional op eration such as addition may also b e required, which can add to the complexity and latency of the divisor multiple generating pro cess.
Recommended publications
  • Data-Level Parallelism
    Fall 2015 :: CSE 610 – Parallel Computer Architectures Data-Level Parallelism Nima Honarmand Fall 2015 :: CSE 610 – Parallel Computer Architectures Overview • Data Parallelism vs. Control Parallelism – Data Parallelism: parallelism arises from executing essentially the same code on a large number of objects – Control Parallelism: parallelism arises from executing different threads of control concurrently • Hypothesis: applications that use massively parallel machines will mostly exploit data parallelism – Common in the Scientific Computing domain • DLP originally linked with SIMD machines; now SIMT is more common – SIMD: Single Instruction Multiple Data – SIMT: Single Instruction Multiple Threads Fall 2015 :: CSE 610 – Parallel Computer Architectures Overview • Many incarnations of DLP architectures over decades – Old vector processors • Cray processors: Cray-1, Cray-2, …, Cray X1 – SIMD extensions • Intel SSE and AVX units • Alpha Tarantula (didn’t see light of day ) – Old massively parallel computers • Connection Machines • MasPar machines – Modern GPUs • NVIDIA, AMD, Qualcomm, … • Focus of throughput rather than latency Vector Processors 4 SCALAR VECTOR (1 operation) (N operations) r1 r2 v1 v2 + + r3 v3 vector length add r3, r1, r2 vadd.vv v3, v1, v2 Scalar processors operate on single numbers (scalars) Vector processors operate on linear sequences of numbers (vectors) 6.888 Spring 2013 - Sanchez and Emer - L14 What’s in a Vector Processor? 5 A scalar processor (e.g. a MIPS processor) Scalar register file (32 registers) Scalar functional units (arithmetic, load/store, etc) A vector register file (a 2D register array) Each register is an array of elements E.g. 32 registers with 32 64-bit elements per register MVL = maximum vector length = max # of elements per register A set of vector functional units Integer, FP, load/store, etc Some times vector and scalar units are combined (share ALUs) 6.888 Spring 2013 - Sanchez and Emer - L14 Example of Simple Vector Processor 6 6.888 Spring 2013 - Sanchez and Emer - L14 Basic Vector ISA 7 Instr.
    [Show full text]
  • Lecture 14: Gpus
    LECTURE 14 GPUS DANIEL SANCHEZ AND JOEL EMER [INCORPORATES MATERIAL FROM KOZYRAKIS (EE382A), NVIDIA KEPLER WHITEPAPER, HENNESY&PATTERSON] 6.888 PARALLEL AND HETEROGENEOUS COMPUTER ARCHITECTURE SPRING 2013 Today’s Menu 2 Review of vector processors Basic GPU architecture Paper discussions 6.888 Spring 2013 - Sanchez and Emer - L14 Vector Processors 3 SCALAR VECTOR (1 operation) (N operations) r1 r2 v1 v2 + + r3 v3 vector length add r3, r1, r2 vadd.vv v3, v1, v2 Scalar processors operate on single numbers (scalars) Vector processors operate on linear sequences of numbers (vectors) 6.888 Spring 2013 - Sanchez and Emer - L14 What’s in a Vector Processor? 4 A scalar processor (e.g. a MIPS processor) Scalar register file (32 registers) Scalar functional units (arithmetic, load/store, etc) A vector register file (a 2D register array) Each register is an array of elements E.g. 32 registers with 32 64-bit elements per register MVL = maximum vector length = max # of elements per register A set of vector functional units Integer, FP, load/store, etc Some times vector and scalar units are combined (share ALUs) 6.888 Spring 2013 - Sanchez and Emer - L14 Example of Simple Vector Processor 5 6.888 Spring 2013 - Sanchez and Emer - L14 Basic Vector ISA 6 Instr. Operands Operation Comment VADD.VV V1,V2,V3 V1=V2+V3 vector + vector VADD.SV V1,R0,V2 V1=R0+V2 scalar + vector VMUL.VV V1,V2,V3 V1=V2*V3 vector x vector VMUL.SV V1,R0,V2 V1=R0*V2 scalar x vector VLD V1,R1 V1=M[R1...R1+63] load, stride=1 VLDS V1,R1,R2 V1=M[R1…R1+63*R2] load, stride=R2
    [Show full text]
  • Vector Vs. Scalar Processors: a Performance Comparison Using a Set of Computational Science Benchmarks
    Vector vs. Scalar Processors: A Performance Comparison Using a Set of Computational Science Benchmarks Mike Ashworth, Ian J. Bush and Martyn F. Guest, Computational Science & Engineering Department, CCLRC Daresbury Laboratory ABSTRACT: Despite a significant decline in their popularity in the last decade vector processors are still with us, and manufacturers such as Cray and NEC are bringing new products to market. We have carried out a performance comparison of three full-scale applications, the first, SBLI, a Direct Numerical Simulation code from Computational Fluid Dynamics, the second, DL_POLY, a molecular dynamics code and the third, POLCOMS, a coastal-ocean model. Comparing the performance of the Cray X1 vector system with two massively parallel (MPP) micro-processor-based systems we find three rather different results. The SBLI PCHAN benchmark performs excellently on the Cray X1 with no code modification, showing 100% vectorisation and significantly outperforming the MPP systems. The performance of DL_POLY was initially poor, but we were able to make significant improvements through a few simple optimisations. The POLCOMS code has been substantially restructured for cache-based MPP systems and now does not vectorise at all well on the Cray X1 leading to poor performance. We conclude that both vector and MPP systems can deliver high performance levels but that, depending on the algorithm, careful software design may be necessary if the same code is to achieve high performance on different architectures. KEYWORDS: vector processor, scalar processor, benchmarking, parallel computing, CFD, molecular dynamics, coastal ocean modelling All of the key computational science groups in the 1. Introduction UK made use of vector supercomputers during their halcyon days of the 1970s, 1980s and into the early 1990s Vector computers entered the scene at a very early [1]-[3].
    [Show full text]
  • Design and Implementation of a Multithreaded Associative Simd Processor
    DESIGN AND IMPLEMENTATION OF A MULTITHREADED ASSOCIATIVE SIMD PROCESSOR A dissertation submitted to Kent State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy by Kevin Schaffer December, 2011 Dissertation written by Kevin Schaffer B.S., Kent State University, 2001 M.S., Kent State University, 2003 Ph.D., Kent State University, 2011 Approved by Robert A. Walker, Chair, Doctoral Dissertation Committee Johnnie W. Baker, Members, Doctoral Dissertation Committee Kenneth E. Batcher, Eugene C. Gartland, Accepted by John R. D. Stalvey, Administrator, Department of Computer Science Timothy Moerland, Dean, College of Arts and Sciences ii TABLE OF CONTENTS LIST OF FIGURES ......................................................................................................... viii LIST OF TABLES ............................................................................................................. xi CHAPTER 1 INTRODUCTION ........................................................................................ 1 1.1. Architectural Trends .............................................................................................. 1 1.1.1. Wide-Issue Superscalar Processors............................................................... 2 1.1.2. Chip Multiprocessors (CMPs) ...................................................................... 2 1.2. An Alternative Approach: SIMD ........................................................................... 3 1.3. MTASC Processor ................................................................................................
    [Show full text]
  • Chapter 4 Data-Level Parallelism in Vector, SIMD, and GPU Architectures
    Computer Architecture A Quantitative Approach, Fifth Edition Chapter 4 Data-Level Parallelism in Vector, SIMD, and GPU Architectures Copyright © 2012, Elsevier Inc. All rights reserved. 1 Contents 1. SIMD architecture 2. Vector architectures optimizations: Multiple Lanes, Vector Length Registers, Vector Mask Registers, Memory Banks, Stride, Scatter-Gather, 3. Programming Vector Architectures 4. SIMD extensions for media apps 5. GPUs – Graphical Processing Units 6. Fermi architecture innovations 7. Examples of loop-level parallelism 8. Fallacies Copyright © 2012, Elsevier Inc. All rights reserved. 2 Classes of Computers Classes Flynn’s Taxonomy SISD - Single instruction stream, single data stream SIMD - Single instruction stream, multiple data streams New: SIMT – Single Instruction Multiple Threads (for GPUs) MISD - Multiple instruction streams, single data stream No commercial implementation MIMD - Multiple instruction streams, multiple data streams Tightly-coupled MIMD Loosely-coupled MIMD Copyright © 2012, Elsevier Inc. All rights reserved. 3 Introduction Advantages of SIMD architectures 1. Can exploit significant data-level parallelism for: 1. matrix-oriented scientific computing 2. media-oriented image and sound processors 2. More energy efficient than MIMD 1. Only needs to fetch one instruction per multiple data operations, rather than one instr. per data op. 2. Makes SIMD attractive for personal mobile devices 3. Allows programmers to continue thinking sequentially SIMD/MIMD comparison. Potential speedup for SIMD twice that from MIMID! x86 processors expect two additional cores per chip per year SIMD width to double every four years Copyright © 2012, Elsevier Inc. All rights reserved. 4 Introduction SIMD parallelism SIMD architectures A. Vector architectures B. SIMD extensions for mobile systems and multimedia applications C.
    [Show full text]
  • Vector Processors
    VECTOR PROCESSORS Computer Science Department CS 566 – Fall 2012 1 Eman Aldakheel Ganesh Chandrasekaran Prof. Ajay Kshemkalyani OUTLINE What is Vector Processors Vector Processing & Parallel Processing Basic Vector Architecture Vector Instruction Vector Performance Advantages Disadvantages Applications Conclusion 2 VECTOR PROCESSORS A processor can operate on an entire vector in one instruction Work done automatically in parallel (simultaneously) The operand to the instructions are complete vectors instead of one element Reduce the fetch and decode bandwidth Data parallelism Tasks usually consist of: Large active data sets Poor locality Long run times 3 VECTOR PROCESSORS (CONT’D) Each result independent of previous result Long pipeline Compiler ensures no dependencies High clock rate Vector instructions access memory with known pattern Reduces branches and branch problems in pipelines Single vector instruction implies lots of work Example: for(i=0; i<n; i++) c(i) = a(i) + b(i); 4 5 VECTOR PROCESSORS (CONT’D) vadd // C code b[15]+=a[15] for(i=0;i<16; i++) b[i]+=a[i] b[14]+=a[14] b[13]+=a[13] b[12]+=a[12] // Vectorized code b[11]+=a[11] set vl,16 b[10]+=a[10] vload vr0,b b[9]+=a[9] vload vr1,a b[8]+=a[8] vadd vr0,vr0,vr1 b[7]+=a[7] vstore vr0,b b[6]+=a[6] b[5]+=a[5] b[4]+=a[4] Each vector instruction b[3]+=a[3] holds many units of b[2]+=a[2] independent operations b[1]+=a[1] 6 b[0]+=a[0] 1 Vector Lane VECTOR PROCESSORS (CONT’D) vadd // C code b[15]+=a[15] 16 Vector Lanes for(i=0;i<16; i++) b[14]+=a[14] b[i]+=a[i]
    [Show full text]
  • Instruction Set Innovations for Convey's HC-1 Computer
    Instruction Set Innovations for Convey's HC-1 Computer THE WORLD’S FIRST HYBRID-CORE COMPUTER. Hot Chips Conference 2009 [email protected] Introduction to Convey Computer • Company Status – Second round venture based startup company – Product beta systems are at customer sites – Currently staffing at 36 people – Located in Richardson, Texas • Investors – Four Venture Capital Investors • Interwest Partners (Menlo Park) • CenterPoint Ventures (Dallas) • Rho Ventures (New York) • Braemar Energy Ventures (Boston) – Two Industry Investors • Intel Capital • Xilinx Presentation Outline • Overview of HC-1 Computer • Instruction Set Innovations • Application Examples Page 3 Hot Chips Conference 2009 What is a Hybrid-Core Computer ? A hybrid-core computer improves application performance by combining an x86 processor with hardware that implements application-specific instructions. ANSI Standard Applications C/C++/Fortran Convey Compilers x86 Coprocessor Instructions Instructions Intel® Processor Hybrid-Core Coprocessor Oil & Gas& Oil Financial Sciences Custom CAE Application-Specific Personalities Cache-coherent shared virtual memory Page 4 Hot Chips Conference 2009 What Is a Personality? • A personality is a reloadable set of instructions that augment x86 application the x86 instruction set Processor specific – Applicable to a class of applications instructions or specific to a particular code • Each personality is a set of files that includes: – The bits loaded into the Coprocessor – Information used by the Convey compiler • List of
    [Show full text]
  • VLIW DSP Vs. Superscalar Implementation of a Baseline H.263
    VLIW DSP VS. SUPERSCALAR IMPLEMENTATION OF A BASELINE H.263 VIDEO ENCODER Serene Banerjee, Hamid R. Sheikh, Lizy K. John, Brian L. Evans, and Alan C. Bovik Dept. of Electrical and Computer Engineering The University of Texas at Austin, Austin, TX 78712-1084 USA fserene,sheikh,ljohn,b evans,b [email protected] ABSTRACT sum-of-absolute di erences SAD calculations. SAD provides a measure of the closeness between a 16 AVery Long Instruction Word VLIW pro cessor and 16 macroblo ck in the current frame and a 16 16 a sup erscalar pro cessor can execute multiple instruc- macroblo ck in the previous frame. Other computa- tions simultaneously. A VLIW pro cessor dep ends on tional complex op erations are image interp olation, im- the compiler and programmer to nd the parallelism age reconstruction, and forward discrete cosine trans- in the instructions, whereas a sup erscaler pro cessor de- form DCT. termines the parallelism at runtime. This pap er com- In this pap er, we evaluate the p erformance of the pares TI TMS320C6700 VLIW digital signal pro cessor C source co de for a research H.263 co dec develop ed at DSP and SimpleScalar sup erscalar implementations the University of British Columbia UBC [4] on two of a baseline H.263 video enco der in C. With level pro cessor architectures. The rst architecture is a very two C compiler optimization, a one-way issue sup er- long instruction word VLIW digital signal pro cessor scalar pro cessor is 7.5 times faster than the VLIW DSP DSP represented by the TI TMS320C6701 [5, 6].
    [Show full text]
  • The RISC-V Instruction Set Manual Volume I: User-Level ISA Document Version 2.2
    The RISC-V Instruction Set Manual Volume I: User-Level ISA Document Version 2.2 Editors: Andrew Waterman1, Krste Asanovi´c1;2 1SiFive Inc., 2CS Division, EECS Department, University of California, Berkeley [email protected], [email protected] May 7, 2017 Contributors to all versions of the spec in alphabetical order (please contact editors to suggest corrections): Krste Asanovi´c,Rimas Aviˇzienis,Jacob Bachmeyer, Christopher F. Batten, Allen J. Baum, Alex Bradbury, Scott Beamer, Preston Briggs, Christopher Celio, David Chisnall, Paul Clayton, Palmer Dabbelt, Stefan Freudenberger, Jan Gray, Michael Hamburg, John Hauser, David Horner, Olof Johansson, Ben Keller, Yunsup Lee, Joseph Myers, Rishiyur Nikhil, Stefan O'Rear, Albert Ou, John Ousterhout, David Patterson, Colin Schmidt, Michael Taylor, Wesley Terpstra, Matt Thomas, Tommy Thorn, Ray VanDeWalker, Megan Wachs, Andrew Waterman, Robert Wat- son, and Reinoud Zandijk. This document is released under a Creative Commons Attribution 4.0 International License. This document is a derivative of \The RISC-V Instruction Set Manual, Volume I: User-Level ISA Version 2.1" released under the following license: c 2010{2017 Andrew Waterman, Yunsup Lee, David Patterson, Krste Asanovi´c. Creative Commons Attribution 4.0 International License. Please cite as: \The RISC-V Instruction Set Manual, Volume I: User-Level ISA, Document Version 2.2", Editors Andrew Waterman and Krste Asanovi´c,RISC-V Foundation, May 2017. Preface This is version 2.2 of the document describing the RISC-V user-level architecture. The document contains the following versions of the RISC-V ISA modules: Base Version Frozen? RV32I 2.0 Y RV32E 1.9 N RV64I 2.0 Y RV128I 1.7 N Extension Version Frozen? M 2.0 Y A 2.0 Y F 2.0 Y D 2.0 Y Q 2.0 Y L 0.0 N C 2.0 Y B 0.0 N J 0.0 N T 0.0 N P 0.1 N V 0.2 N N 1.1 N To date, no parts of the standard have been officially ratified by the RISC-V Foundation, but the components labeled \frozen" above are not expected to change during the ratification process beyond resolving ambiguities and holes in the specification.
    [Show full text]
  • GPU Architecture and Programming
    GPU Architecture and Programming Andrei Doncescu inspired by NVIDIA Traditional Computing Von Neumann architecture: instructions are sent from memory to the CPU Serial execution: Instructions are executed one after another on a single Central Processing Unit (CPU) Problems: • More expensive to produce •More expensive to run •Bus speed limitation Parallel Computing Official-sounding definition: The simultaneous use of multiple compute resources to solve a computational problem. Benefits: • Economical – requires less power !!! and cheaper to produce • Better performance – bus/bottleneck issue Limitations: • New architecture – Von Neumann is all we know! • New debugging difficulties – cache consistency issue Processes and Threads • Traditional process – One thread of control through a large, potentially sparse address space – Address space may be shared with other processes (shared mem) – Collection of systems resources (files, semaphores) • Thread (light weight process) – A flow of control through an address space – Each address space can have multiple concurrent control flows – Each thread has access to entire address space – Potentially parallel execution, minimal state (low overheads) – May need synchronization to control access to shared variables Threads • Each thread has its own stack, PC, registers – Share address space, files,… Flynn’s Taxonomy Classification of computer architectures, proposed by Michael J. Flynn •SISD – traditional serial architecture in computers. •SIMD – parallel computer. One instruction is executed many times
    [Show full text]
  • CSC506 Lecture 7 Vector Processors
    Vector Processors A vector processor is a pipelined processor with special instructions designed to keep the (floating point) execution unit pipeline(s) full. These special instructions are vector instructions. Terminology: ¨ Scalar – a single quantity (number). ¨ Vector – an ordered series of scalar quantities – a one-dimensional array. Scalar Quantity Data Vector Quantity Data Data Data Data Data Data Data Data Five basic types of vector operations: 1. V ß V Example: Complement all elements 2. S ß V Examples: Min, Max, Sum 3. V ß V x V Examples: Vector addition, multiplication, division 4. V ß V x S Examples: Multiply or add a scalar to a vector 5. S ß V x V Example: Calculate an element of a matrix One instruction says, in effect, do the same thing on all the elements of the vector(s). Vector Processors Architecture of Parallel Computers Page 1 The generic vector processor: Stream A Pipelined Processor Stream B Multiport Memory System Stream C = A x B Many large-scale scientific and engineering problems can be solved by operations on large vectors or matrices of floating point numbers. Vector processors are designed to efficiently work on these problems. Performance of these machines is measured in: ¨ FLOPS – Floating Point Operations per Second, ¨ MegaFLOPS – a million FLOPS, or ¨ GigaFLOPS – a billion FLOPS. The extremely high performance is achieved only for problems that can be expressed as operations on large vectors. These processors are also called supercomputers, popularized by the CRAY series. The cost/performance ratio of vector processors can be impressive, but the initial cost is high (few of them are built).
    [Show full text]
  • Computer Architecture and Design
    0885_frame_C05.fm Page 1 Tuesday, November 13, 2001 6:33 PM 5 Computer Architecture and Design 5.1 Server Computer Architecture .......................................... 5-2 Introduction • Client–Server Computing • Server Types • Server Deployment Considerations • Server Architecture • Challenges in Server Design • Summary 5.2 Very Large Instruction Word Architectures ................... 5-10 What Is a VLIW Processor? • Different Flavors of Parallelism • A Brief History of VLIW Processors • Defoe: An Example VLIW Architecture • The Intel Itanium Processor • The Transmeta Crusoe Processor • Scheduling Algorithms for VLIW 5.3 Vector Processing.............................................................. 5-22 Introduction • Data Parallelism • History of Data Parallel Machines • Basic Vector Register Architecture • Vector Jean-Luc Gaudiot Instruction Set Advantages • Lanes: Parallel Execution University of Southern California Units • Vector Register File Organization • Traditional Vector Computers versus Microprocessor Multimedia Extensions • Siamack Haghighi Memory System Design • Future Directions • Conclusions Intel Corporation 5.4 Multithreading, Multiprocessing..................................... 5-32 Binu Matthew Introduction • Parallel Processing Software Framework • University of Utah Parallel Processing Hardware Framework • Concluding Remarks • To Probe Further • Acknowledgments Krste Asanovic 5.5 Survey of Parallel Systems ............................................... 5-48 MIT Laboratory for Computer Introduction • Single Instruction
    [Show full text]