DOCSLIB.ORG

GCC for Embedded Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

GCC for Embedded Systems Ayal Zaks IBM Haifa Research Lab [email protected] http://www.haifa.il.ibm.com/dept/svt/code_compiler.html IBM Haifa Research Lab IBM Haifa Research Lab GCC for Embedded Systems – Talk Goals GCC for Embedded Systems – why GCC? What (R&D) are we doing in GCC? Where can you learn more? 2 IBM Haifa Research Lab GCC for Embedded Systems - Talk Layout 1. GCC – development: open community product of FSF 2. GCC – recent contributions from IBM Haifa Vectorization (GCC 4.0) Modulo scheduling (GCC 4.0) Inter-Procedural constant propagation (GCC 4.1) Data-layout optimizations (GCC 4.3) 3. GCC – performance for embedded: EEMBC 4. GCC – research: HiPEAC 3 IBM Haifa Research Lab GCC development – Mission Statement (from http://gcc.gnu.org/gccmission.html) GCC development is a part of the GNU Project , aiming to improve the compiler used in the GNU system including the GNU/Linux® variant. The GCC development effort uses an open development environment and supports many other platforms in order to foster a world-class optimizing compiler , to attract a larger team of developers, to ensure that GCC and the GNU system work on multiple architectures and diverse environments , and to more thoroughly test and extend the features of GCC. 4 IBM Haifa Research Lab GNU Compiler Collection Advantages Consistent across large number of targets (target is architecture plus operating system) Very good warnings aid porting to new targets Free software project: licenses protect GCC as free software while allowing users to build proprietary software doesn't depend on any one organization developers have deep commitment to GCC many choices for commercial support Continuous improvement 5 IBM Haifa Research Lab Computer Architectures Aspects of support instructions, registers, memory CPU tuning parameters Architectures GCC supports 68HC11 68HC12 Alpha AMD64 ARC ARM AVR Blackfin CRIS CRX C4x D30V FR-30 FR-V H8/300 IA-32 IPF (IA-64) IQ2000 M32C M32R M68000 M88000 MCORE MIPS MMIX MN10300 PA-RISC PowerPC® PowerPC64 ROMP S/390® SH SPARC SPARC-V9 Stormy16 V850 VAX Xscale Xtensa z/Architecture™ Cell 6 IBM Haifa Research Lab GCC – GNU Compiler Collection Free Software Foundation (FSF) 2.3 million lines of code, 20 years of development (since 1987) Multiple programming languages C, C++, Objective-C, Ada, Java, Fortran Multiplatform: Multiple target processors and operating systems IBM eServers, RISC, embedded, ... (over 30 architectures!) Linux , Unix, Windows, OS/X, embedded, ... GCC is de-facto standard in the Linux eco-system 7 IBM Haifa Research Lab GCC – Development Process Legal Issues Copyright held by the FSF (assignments required!) Licensed under the GPL Who’s involved Volunteers Academia Linux distros RedHat, Novell/SUSE IBM IBM LTC Haifa Lab IBM Research Vendors: CodeSourcery, ARM, AdaCore, more 8 IBM Haifa Research Lab GCC for Embedded Systems - Talk Layout 1. GCC – development: product of Free Software Foundation community 2. GCC – recent contributions from IBM Haifa Vectorization (GCC 4.0) Modulo scheduling (GCC 4.0) Inter-Procedural constant propagation (GCC 4.1) Data-layout optimizations (GCC 4.3) 3. GCC – performance for embedded: EEMBC 4. GCC – research: HiPEAC 9 IBM Haifa Research Lab (http://www.gccsummit.org/2004/speakers.php) 10 IBM Haifa Research Lab Programming for Vector Machines Proliferation of SIMD (Single Instruction Multiple Data) model MMX/SSE, Altivec Communications, Video, Gaming Fortran90 a[0:N] = b[0:N] + c[0:N]; Intrinsics vector float vb = vec_load (0, ptr_b); vector float vc = vec_load (0, ptr_c); vector float va = vec_add (vb, vc); vec_store (va, 0, ptr_a); Autovectorization : Automatically transform serial code to vector code by the compiler. 11 IBM Haifa Research Lab Vectorization original serial loop: loop in vector notation: for(i=0; i<N; i++){ for (i=0; i<(N-N% VF ); i+= VF ){ a[i] = a[i] + b[i]; vectorization a[i:i+ VF ] = a[i:i+ VF ] + b[i:i+ VF ]; } } vectorized loop loop in vector notation: for ( ; i < N; i++) { for (i=0; i<N; i+= VF ){ a[i] = a[i] + b[i]; a[i:i+ VF ] = a[i:i+ VF ] + b[i:i+ VF ]; } epilog loop } 12 IBM Haifa Research Lab Vectorization Examples Pixel Blending Application - small dataset: 16x improvement - tiled large dataset: 7x improvement - large dataset with display: 3x improvement for (i = 0; i < sampleCount; i++) { output[i] = ( (input1[i] * α)>>8 + (input2[i] * ( α-1))>>8 ); } SPEC gzip – 9% improvement for (n = 0; n < SIZE; n++) { lvx v0,r3,r2 m = head[n]; vsubuhs v0,v0,v1 head[n] = (m >= WSIZE ? m-WSIZE : 0); stvx v0,r3,r2 } addi r2,r2,16 bdnz L2 13 IBM Haifa Research Lab GCC Developers’ Summit 2005 (http://www.gccsummit.org/2005/speakers.php) 14 IBM Haifa Research Lab GCC Developers’ Summit 2006 (http://www.gccsummit.org/2006/speakers.php) 15 IBM Haifa Research Lab GCC for Embedded Systems - Talk Layout 1. GCC – development: product of Free Software Foundation community 2. GCC – recent contributions from IBM Haifa Vectorization (GCC 4.0) Modulo scheduling (GCC 4.0) Inter-Procedural constant propagation (GCC 4.1) Data-layout optimizations (GCC 4.3) 3. GCC – performance for embedded: EEMBC 4. GCC – research: HiPEAC 16 IBM Haifa Research Lab EEMBC Reports Record-Breaking Telecom Benchmark Scores for IBM PowerPC 970FX 2-GHz Processor “EL DORADO HILLS, Calif.—Aug. 21, 2006—The Embedded Microprocessor Benchmark Consortium today announced certified EEMBC benchmark scores for the IBM PowerPC 970FX which set a new record for embedded processors tested against the consortium’s TeleBench™ telecommunications benchmark suite. The IBM PowerPC 970FX, clocked at 2 GHz and using the GCC auto-vectorization compiler , with full-fury optimizations for Vector/SIMD Multimedia Extension Technology, achieved a score of 1058.7 Telemarks. In out- of-the-box tests, the PowerPC 970FX achieved a score of 141.8 Telemarks, a 182% improvement over a previous record-setting score for the same device obtained with a different compiler. ... "High-end processors are being used in more embedded products than ever, and OEMs are looking for benchmark scores that offer a more application-specific indication of performance than traditional server benchmarks," said Markus Levy, EEMBC president. "By publishing these TeleBench scores for its PowerPC 970FX, IBM is showing its commitment to providing customers with valuable, trustworthy information on processor performance. Beyond delivering a realistic picture of how its device will perform in communications applications, the scores also represent a convincing indication of the performance advantages provided by vector processing in general.“ For this new round of PowerPC 970FX benchmark tests, and in accordance with EEMBC rules for optimization, IBM Research improved the GCC auto-vectorization compiler and IBM's Power Architecture Performance Team modified the EEMBC benchmark source code to use the VMX instructions documented in the PowerPC Microprocessor Family: Vector/SIMD Multimedia Extension Technology Programming Environments Manual. … Detailed score reports for the PowerPC 970FX are available free on the EEMBC web site at www.eembc.org.” (taken from: http://www.eembc.org/Press/PressRelease/060821.htm) 17 IBM Haifa Research Lab EEMBC: The Embedded Microprocessor Benchmark Consortium (http://www.eembc.org) 18 IBM Haifa Research Lab GCC for Embedded Systems - Talk Layout 1. GCC – development: product of Free Software Foundation community 2. GCC – recent contributions from IBM Haifa Vectorization (GCC 4.0) Modulo scheduling (GCC 4.0) Inter-Procedural constant propagation (GCC 4.1) Data-layout optimizations (GCC 4.3) 3. GCC – performance for embedded: EEMBC 4. GCC – research: HiPEAC 19 IBM Haifa Research Lab HiPEAC (www.hipeac.net) 20 IBM Haifa Research Lab 21 IBM Haifa Research Lab References GCC on the Free Software Foundation website: gcc.gnu.org (plus wiki) www.gccsummit.org (including paper proceedings) HiPEAC GCC Tutorials: http://www.hipeac.net/gcc-tutorial Recent Academic Papers "Auto-Vectorization of Interleaved Data for SIMD", Dorit Nuzman, Ira Rosen, and Ayal Zaks, PLDI , June 12-14, 2006, Ottawa, Canada "Multi-platform Auto-vectorization", Dorit Nuzman and Richard Henderson, CGO- 4, March 26-29, 2006, Manhattan, New York Thread-level speculation: PPoPP’06 [Liu et al.] and ICS’05 [Renau et al.] Induction variable recognition: HiPEAC’05 [Pop et al.] LLVM - life-long adaptive optimization: CGO’04 [Lattner and Adve] Generic programming (template metaprogramming and concepts): PoPL’06 [Dos Reis and Stroustrup] “Contributions to the GNU Compiler Collection GCC”, IBM’s Systems Journal, issue on Open Source, volume 44, number 2, 2005 22 IBM Haifa Research Lab GCC for Embedded Systems – Talk Goals GCC for Embedded Systems – why GCC? What (R&D) are we doing in GCC? Where can you learn more? thanks ! 23.
Recommended publications
  • Chapter 8 Instruction Set

    Chapter 8 Instruction Set

    Chapter 8 Instruction Set 80 80 This chapter lists the PowerPC instruction set in alphabetical order by mnemonic. Note that each entry includes the instruction formats and a quick reference ‘legend’ that provides such information as the level(s) of the PowerPC architecture in which the instruction may be found—user instruction set architecture (UISA), virtual environment architecture U (VEA), and operating environment architecture (OEA); and the privilege level of the V instruction—user- or supervisor-level (an instruction is assumed to be user-level unless the O legend specifies that it is supervisor-level); and the instruction formats. The format diagrams show, horizontally, all valid combinations of instruction fields; for a graphical representation of these instruction formats, see Appendix A, “PowerPC Instruction Set Listings.” The legend also indicates if the instruction is 64-bit, , 64-bit bridge, and/or optional. A description of the instruction fields and pseudocode conventions are also provided. For more information on the PowerPC instruction set, refer to Chapter 4, “Addressing Modes and Instruction Set Summary.” Note that the architecture specification refers to user-level and supervisor-level as problem state and privileged state, respectively. 8.1 Instruction Formats Instructions are four bytes long and word-aligned, so when instruction addresses are U presented to the processor (as in branch instructions) the two low-order bits are ignored. Similarly, whenever the processor develops an instruction address, its two low-order bits are zero. Bits 0–5 always specify the primary opcode. Many instructions also have an extended opcode. The remaining bits of the instruction contain one or more fields for the different instruction formats.
  • Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced PowerPC Architecture Version 1.0 May 7, 2002 Third Edition (Dec 2001) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. IBM does not warrant that the use of the information herein shall be free from third party intellectual property claims. IBM does not warrant that the contents of this document will meet your requirements or that the document is error-free. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the document. IBM may make improvements and or changes in the product(s) and/or program(s) described in this document at any time. This document does not imply a commitment by IBM to supply or make generally available the product(s) described herein. No part of this document may be reproduced or distributed in any form or by any means, or stored in a data base or retrieval system, without the written permission of IBM. Address comments about this document to: IBM Corporation Department B5H / Building 667 3039 Cornwallis Road P.O. Box 12195 Research Triangle Park, NC 27709 Portions of the information in this document may have been published previously in the following related documents: The PowerPC Architecture: A Specification for a New Family of RISC Processors, Second Edition (1994) The IBM PowerPC Embedded Environment: Architectural Specifications for IBM PowerPC Embedded Controllers, Second Edition (1998) IBM may have patents or pending patent applications covering the subject matter in this document.
  • SPARC/IOBP-CPU-56 Installation Guide

    SPARC/IOBP-CPU-56 Installation Guide

    SPARC/IOBP-CPU-56 Installation Guide P/N 220226 Revision AB September 2003 Copyright The information in this publication is subject to change without notice. Force Computers, GmbH reserves the right to make changes without notice to this, or any of its products, to improve reliability, performance, or design. Force Computers, GmbH shall not be liable for technical or editorial errors or omissions contained herein, nor for indirect, special, incidental, or consequential damages resulting from the furnishing, performance, or use of this material. This information is provided "as is" and Force Computers, GmbH expressly disclaims any and all warranties, express, implied, statutory, or otherwise, including without limitation, any express, statutory, or implied warranty of merchantability, fitness for a particular purpose, or non−infringement. This publication contains information protected by copyright. This publication shall not be reproduced, transmitted, or stored in a retrieval system, nor its contents used for any purpose, without the prior written consent of Force Computers, GmbH. Force Computers, GmbH assumes no responsibility for the use of any circuitry other than circuitry that is part of a product of Force Computers, GmbH. Force Computers, GmbH does not convey to the purchaser of the product described herein any license under the patent rights of Force Computers, GmbH nor the rights of others. CopyrightE 2003 by Force Computers, GmbH. All rights reserved. The Force logo is a trademark of Force Computers, GmbH. IEEER is a registered trademark of the Institute for Electrical and Electronics Engineers, Inc. PICMGR, CompactPCIR, and the CompactPCI logo are registered trademarks and the PICMG logo is a trademark of the PCI Industrial Computer Manufacturer’s Group.
  • Schedule 14A Employee Slides Supertex Sunnyvale

    Schedule 14A Employee Slides Supertex Sunnyvale

    UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 SCHEDULE 14A Proxy Statement Pursuant to Section 14(a) of the Securities Exchange Act of 1934 Filed by the Registrant Filed by a Party other than the Registrant Check the appropriate box: Preliminary Proxy Statement Confidential, for Use of the Commission Only (as permitted by Rule 14a-6(e)(2)) Definitive Proxy Statement Definitive Additional Materials Soliciting Material Pursuant to §240.14a-12 Supertex, Inc. (Name of Registrant as Specified In Its Charter) Microchip Technology Incorporated (Name of Person(s) Filing Proxy Statement, if other than the Registrant) Payment of Filing Fee (Check the appropriate box): No fee required. Fee computed on table below per Exchange Act Rules 14a-6(i)(1) and 0-11. (1) Title of each class of securities to which transaction applies: (2) Aggregate number of securities to which transaction applies: (3) Per unit price or other underlying value of transaction computed pursuant to Exchange Act Rule 0-11 (set forth the amount on which the filing fee is calculated and state how it was determined): (4) Proposed maximum aggregate value of transaction: (5) Total fee paid: Fee paid previously with preliminary materials. Check box if any part of the fee is offset as provided by Exchange Act Rule 0-11(a)(2) and identify the filing for which the offsetting fee was paid previously. Identify the previous filing by registration statement number, or the Form or Schedule and the date of its filing. (1) Amount Previously Paid: (2) Form, Schedule or Registration Statement No.: (3) Filing Party: (4) Date Filed: Filed by Microchip Technology Incorporated Pursuant to Rule 14a-12 of the Securities Exchange Act of 1934 Subject Company: Supertex, Inc.
  • Implementing Powerpc Linux on System I Platform

    Implementing Powerpc Linux on System I Platform

    Front cover Implementing POWER Linux on IBM System i Platform Planning and configuring Linux servers on IBM System i platform Linux distribution on IBM System i Platform installation guide Tips to run Linux servers on IBM System i platform Yessong Johng Erwin Earley Rico Franke Vlatko Kosturjak ibm.com/redbooks International Technical Support Organization Implementing POWER Linux on IBM System i Platform February 2007 SG24-6388-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (February 2007) This edition applies to i5/OS V5R4, SLES10 and RHEL4. © Copyright International Business Machines Corporation 2005, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Chapter 1. Introduction to Linux on System i platform . 1 1.1 Concepts and terminology . 2 1.1.1 System i platform . 2 1.1.2 Hardware management console . 4 1.1.3 Virtual Partition Manager (VPM) . 10 1.2 Brief introduction to Linux and Linux on System i platform . 12 1.2.1 Linux on System i platform . 12 1.3 Differences between existing Power5-based System i and previous System i models 13 1.3.1 Linux enhancements on Power5 / Power5+ . 14 1.4 Where to go for more information . 15 Chapter 2. Configuration planning . 17 2.1 Concepts and terminology . 18 2.1.1 Processor concepts .
  • A Developer's Guide to the POWER Architecture

    A Developer's Guide to the POWER Architecture

    http://www.ibm.com/developerworks/linux/library/l-powarch/ 7/26/2011 10:53 AM English Sign in (or register) Technical topics Evaluation software Community Events A developer's guide to the POWER architecture POWER programming by the book Brett Olsson , Processor architect, IBM Anthony Marsala , Software engineer, IBM Summary: POWER® processors are found in everything from supercomputers to game consoles and from servers to cell phones -- and they all share a common architecture. This introduction to the PowerPC application-level programming model will give you an overview of the instruction set, important registers, and other details necessary for developing reliable, high performing POWER applications and maintaining code compatibility among processors. Date: 30 Mar 2004 Level: Intermediate Also available in: Japanese Activity: 22383 views Comments: The POWER architecture and the application-level programming model are common across all branches of the POWER architecture family tree. For detailed information, see the product user's manuals available in the IBM® POWER Web site technical library (see Resources for a link). The POWER architecture is a Reduced Instruction Set Computer (RISC) architecture, with over two hundred defined instructions. POWER is RISC in that most instructions execute in a single cycle and typically perform a single operation (such as loading storage to a register, or storing a register to memory). The POWER architecture is broken up into three levels, or "books." By segmenting the architecture in this way, code compatibility can be maintained across implementations while leaving room for implementations to choose levels of complexity for price/performances trade-offs. The levels are: Book I.
  • M32R Family Software Manual MITSUBISHI 32-BIT SINGLE-CHIP MICROCOMPUTER

    M32R Family Software Manual MITSUBISHI 32-BIT SINGLE-CHIP MICROCOMPUTER

    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
  • LSU EE 4720 Homework 1 Solution Due: 3 March 2006

    LSU EE 4720 Homework 1 Solution Due: 3 March 2006

    LSU EE 4720 Homework 1 Solution Due: 3 March 2006 Several Web links appear below and at least one is long, to avoid the tedium of typing them view the assignment in Adobe reader and click. Problem 1: Consider these add instructions in three common ISAs. (Use the ISA manuals linked to the references page, http://www.ece.lsu.edu/ee4720/reference.html.) # MIPS64 addu r1, r2, r3 # SPARC V9 add g2, g3, g1 # PA RISC 2 add r1, r2, r3 (a) Show the encoding (binary form) for each instruction. Show the value of as many bits as possible. Codings shown below. For PA-RISC the ea, ec, and ed ¯elds are labeled e1, e2, and e3, respectively in the instruction descriptions. There is no label for the eb ¯eld in the instruction description of the add and yes it would make sense to use e0 instead of e1 but they didn't for whatever reason. opcode rs rt rd sa func MIPS64: 0 2 3 1 0 0x21 31 26 25 21 20 16 15 11 10 6 5 0 op rd op3 rs1 i asi rs2 SPARC V9: 2 1 0 2 0 0 3 31 30 29 25 24 19 18 14 13 13 12 5 4 0 OPCD r2 r1 c f ea eb ec ed d t PA-RISC 2: 2 3 2 0 0 01 1 0 00 0 1 0 5 6 10 11 15 16 18 19 19 20 21 22 22 23 23 24 25 26 26 27 31 (b) Identify the ¯eld or ¯elds in the SPARC add instruction which are the closest equivalent to MIPS' func ¯eld.
  • Ross Technology RT6224K User Manual 1 (Pdf)

    Ross Technology RT6224K User Manual 1 (Pdf)

    Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Ross Technology RT6224K-200/512S at our website: Click HERE 830-0016-03 Rev A 11/15/96 PRELIMINARY Colorado 4 RT6224K hyperSPARC CPU Module Features D Based on ROSS’ fifth-generation D SPARC compliant — Zero-wait-state, 512-Kbyte or hyperSPARC processor — SPARC Instruction Set Architec- 1-Mbyte 2nd-level cache — RT620D Central Processing Unit ture (ISA) Version 8 compliant — Demand-paged virtual memory (CPU) — Conforms to SPARC Reference management — RT626 Cache Controller, Memory MMU Architecture D Module design Management, and Tag Unit — Conforms to SPARC Level 2 MBus — MBus-standard form factor: 3.30” (CMTU) Module Specification (Revision 1.2) (8.34 cm) x 5.78” (14.67 cm) — Four (512-Kbyte) or eight D Dual-clock architecture — Provides CPU upgrade path at (1-Mbyte) RT628 Cache Data Units module level (CDUs) Ċ CPU scaleable up to
  • Mi!!Lxlosalamos SCIENTIFIC LABORATORY

    Mi!!Lxlosalamos SCIENTIFIC LABORATORY

    LA=8902-MS C3b ClC-l 4 REPORT COLLECTION REPRODUCTION COPY VAXNMS Benchmarking 1-’ > .— u) 9 g .— mi!!lxLOS ALAMOS SCIENTIFIC LABORATORY Post Office Box 1663 Los Alamos. New Mexico 87545 — wAifiimative Action/Equal Opportunity Employer b . l)lS(”L,\l\ll K “Thisreport wm prcpmd J, an xcttunt ,,1”wurk ,pmwrd by an dgmcy d the tlnitwl SIdtcs (kvcm. mm:. Ncit her t hc llniml SIJIL.. ( Lwcrnmcm nor any .gcncy tlhmd. nor my 08”Ihcif cmployccs. makci my wur,nly. mprcss w mphd. or JwImL.s m> lcg.d Iululity ur rcspmuhdily ltw Ilw w.cur- acy. .vmplctcncs. w uscftthtc>. ttt”any ml’ormdt ml. dpprdl us. prudu.i. w proccw didowd. or rep. resent%Ihd IIS us wuukl not mfrm$e priwtcly mvnd rqdtts. Itcl”crmcti herein 10 my sp.xi!l tom. mrcial ptotlucr. prtxcm. or S.rvskc hy tdc mmw. Irdcnmrl.. nmu(a.lurm. or dwrwi~.. does nut mmwsuily mnstitutc or reply its mdursmwnt. rccummcnddton. or favorin: by the llniwd States (“mvcmment ormy qxncy thctcd. rhc V!C$VSmd opinmm d .mthor% qmxd herein do nut net’. UMrily r;~lt or died lhow. ol”the llnttcd SIJIL.S( ;ovwnnwnt or my ugcncy lhure of. UNITED STATES .. DEPARTMENT OF ENERGY CONTRACT W-7405 -ENG. 36 . ... LA-8902-MS UC-32 Issued: July 1981 G- . VAX/VMS Benchmarking Larry Creel —. I . .._- -- ----- ,. .- .-. .: .- ,.. .. ., ..,..: , .. .., . ... ..... - .-, ..:. .. *._–: - . VAX/VMS BENCHMARKING by Larry Creel ABSTRACT Primary emphasis in this report is on the perform- ance of three Digital Equipment Corporation VAX-11/780 computers at the Los Alamos National Laboratory. Programs used in the study are part of the Laboratory’s set of benchmark programs.
  • SPARC Assembly Language Reference Manual

    SPARC Assembly Language Reference Manual

    SPARC Assembly Language Reference Manual 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business 1995 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from UNIX Systems Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s Suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark of Novell, Inc.
  • Embedded Electronic Coding System

    Embedded Electronic Coding System

    1 GUARD FOR BLIND PEOPLE GUARD FOR BLIND PEOPLE ELECTRONICS AND COMMUNICATION LITAM 2 GUARD FOR BLIND PEOPLE ABSTRACT Aim of this project is to design and develop the electronic guard for blind people on embedded plat form. This project was developed for keep the right way for blind people. It has two important units; they are object detecting sensor unit and micro-controller alarm unit. The object detecting sensor is sense the opposite objects, if the blind person is going to hit any object, the sensor sense that object and given to controller. The controller activates the driver circuit; it will produce the alarm sound, now the people easily identify the opposite object. ELECTRONICS AND COMMUNICATION LITAM 3 GUARD FOR BLIND PEOPLE CHAPTER 1 INTRODUCTION ELECTRONICS AND COMMUNICATION LITAM 4 GUARD FOR BLIND PEOPLE 1.1 METHODOLOGY OF STUDY An embedded based electronic code locking system is designed and implemented using PIC Micro controller to make security. The entire project was developed under embedded systems. EMBEDDED SYSTEMS: A system is something that maintains its existence and functions as a whole through the interaction of its parts. E.g. Body, Mankind, Access Control, etc A system is a part of the world that a person or group of persons during some time interval and for some purpose choose to regard as a whole, consisting of interrelated components, each component characterized by properties that are selected as being relevant to the purpose. • Embedded System is a combination of hardware and software used to achieve a single specific task. • Embedded systems are computer systems that monitor, respond to, or control an external environment.