Vector Câ•Fla Vector Processing Language
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Contrpl Data Nos Version 2 Administration Handbook
60459840 CONTRPL DATA NOS VERSION 2 ADMINISTRATION HANDBOOK /fP^v CDC® OPERATING SYSTEMS: CYBER 180 CYBER 170 CYBER 70 MODELS 71, 72, 73, 74 6000 REVISION RECORD T-gSZBZaSESEl jiito wminan REVISION DESCRIPTION Manual released; reflects NOS 2.3 at PSR level 617. Features include default charge restriction, (10-05-84) terminal input and output count at logoff, password randomization, a new CHARGE directive for the SUBMIT command, and support of the Mass Storage Archival Subsystem. Supports CYBER 180 computer systems. B Revision B reflects NOS 2.4.2 at PSR level 642. It incorporates new features such as support of (09-26-85) CYBER 180 Models 840, 850, 860, and 990, Printer Support Utility, and NAM Application Switching. Revision C reflects NOS 2.5.1 at PSR level 664. It documents the personal identification (09-30-86) v a l i d a t i o n , t h e s i n g l e t e r m i n a l s e s s i o n r e s t r i c t i o n , a n d o t h e r m i s c e l l a n e o u s t e c h n i c a l c h a n g e s . Revision D reflects NOS 2.6.1 at PSR level 700. It includes miscellaneous corrections and minor (04-14-88) additions. Publication No, 60459840 REVISION LETTERS I. O. Q. S. X AND Z ARE NOT USED. Address comments concerning this manual to: Control Data Technical Publications 4201 N. -
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. -
Conversion of the COBRA-IV-I Code from CDC CYBER to HP 9000/700 Version
KAERI/TR-803/97 Conversion of the COBRA-IV-I Code from CDC CYBER to HP 9000/700 Version CDC CYBER Version COBRA-IV-I ^H HP 9000/700 Version ° 1997. 1 Korea Atomic Energy Research Institute £- JiJL>Hl- "CDC CYBER Version COBRA-IV-I 3.B.4) HP 9000/700 Version ±£-2\ ^^" o\] 1997 tf 71 «V Abstract COBRA-IV-I is a multichannel analysis code for the thermal-hydraulic analysis of rod bundle nuclear fuel elements and cores based on the subchannel approach. The existing COBRA-IV-I code is the Control Data Corporation (CDC) CYBER version, which has limitations on the computer core storage and gives some inconvenience to the user interface. To solve these problems, we have converted the COBRA-IV-I code from the CDC CYBER mainframe to an Hewlett Packard (HP) 9000/700-series workstation version, and have verified the converted code. As a result, we have found almost no difference between the two versions in their calculation results. Therefore we expect the HP 9000/700 version of the COBRA-IV-I code to be the basis for the future development of an improved multichannel analysis code under the more convenient user environment. COBRA-IV-I fe COBRA-IV-I £• CDC CYBER-§- SE CDC CYBER oflSlH COBRA-IV-I SHf HP 9000/700 HP 9000/700 -§--^- COBRA-IV-I 3-E.t: ^± Table of Contents Abstract 2 Abstract (in Korean) 3 Table of Contents 4 List of Tables 6 List of Figures 7 1. Introduction 8 2. Conversion of COBRA-IV-1 9 2.1 Precision 9 2.2 Convenience 12 2.3 Emulation 12 2.4 Syntax 13 2.5 Equivalence 17 3. -
ABSTRACT CO-RESIDENT OPERATING SYSTEMS TASK TEAM REPORT April 181 1973
ABSTRACT CO-RESIDENT OPERATING SYSTEMS TASK TEAM REPORT THIS DOCUI-lENT CONTAINS INFORl-lATiON PROPRIETARY TO THE NATIONAL CASH REGISTER COfoIPAflY AND CONTROL DATA CORPORATION. ITS CONTENTS SHALL NOT BE DIVULGED OUTSIDE OF EITHER CO~lPANY NOR REPROD~CED mTHOUT EXPLICIT PERloJISSION OF THE DIRECTOR AND GENERAL r-lANAGER. NCRICDC ADVANCED SYSTEfolS LABORATORY. April 18 1 1973 · 1 The mission of the co-resident oper.al"ing system task group was: "To define a cost effective mechamism within the new operating system to allow selected 01 d operating syst'ems to operate in their entirety permitting simultaneous execution with no modifications to the old operating system". Four people were assigned to this task, I:wo from NCR wifh ,expBrience on/he NCi\/Century and two from CDC experienced with CYI3ER 70 computer systems. The scope of the probl em was narrowed to a point where productive OLltput could be obtained in the allotted time frame. It was decided the' time could be spent most profitably in a detailad study of emulating the .NCR Century computer systems ,on the IPL.·· This decision was heavily influen'ced by a desire to deal with specific problems , ' ral·her·than'philosophi'cal-cmd incondusive'mattcrs. It was also:f.;:;lt thut The productivity of the team would be greater if it were kept s.mall •. Having limited the problom in scope, vario~sassumptions h.od t:)bo made bdore furi-h.:,:,r progress could be accompl ished. Key in this area wes the assumption thar. ;h:; probkm wos soluble. As a result I Ihe team concentroted on how to effect Iheimp\ernentation, as opposed j'O if if' was possibl e. -
Calling Convention
ESWEEK Tutorial 4 October 2015, Amsterdam, Netherlands Lucas Davi, Christopher Liebchen, Ahmad-Reza Sadeghi CASED, Technische Universität Darmstadt Intel Collaborative Research Institute for Secure Computing at TU Darmstadt, Germany http://trust.cased.de/ Motivation • Sophisticated, complex • Various of different developers • Native Code Large attack surface for runtime attacks [Úlfar Erlingsson, Low-level Software Security: Attacks and Defenses, TR 2007] Introduction Vulnerabilities Programs continuously suffer from program bugs, e.g., a buffer overflow Memory errors CVE statistics; zero-day In this tutorial Runtime Attack Exploitation of program vulnerabilities to perform malicious program actions Control-flow attack; runtime exploit Three Decades of Runtime Attacks return-into- Return-oriented Morris Worm libc programming Continuing Arms 1988 Solar Designer Shacham Race 1997 CCS 2007 … Borrowed Code Code Chunk Injection Exploitation AlephOne Krahmer 1996 2005 Are these attacks relevant? Relevance and Impact High Impact of Attacks • Web browsers repeatedly exploited in pwn2own contests • Zero-day issues exploited in Stuxnet/Duqu [Microsoft, BH 2012] • iOS jailbreak Industry Efforts on Defenses • Microsoft EMET (Enhanced Mitigation Experience Toolkit) includes a ROP detection engine • Microsoft Control Flow Guard (CFG) in Windows 10 • Google‘s compiler extension VTV (vitual table verification) Hot Topic of Research • A large body of recent literature on attacks and defenses Stagefright [Drake, BlackHat 2015] These issues in Stagefright -
Porting GCC for Dunces
Porting GCC for Dunces Hans-Peter Nilsson∗ May 21, 2000 ∗Email: <[email protected]>. Thanks to Richard Stallman <[email protected]> for guidance to letting this document be more than a master's thesis. 1 2 Contents 1 Legal notice 11 2 Introduction 13 2.1 Background . 13 2.1.1 Compilers . 13 2.2 This work . 14 2.2.1 Result . 14 2.2.2 Porting . 14 2.2.3 Restrictions in this document . 14 3 The target system 17 3.1 The target architecture . 17 3.1.1 Registers . 17 3.1.2 Sizes . 18 3.1.3 Addressing modes . 18 3.1.4 Instructions . 19 3.2 The target run-time system and libraries . 21 3.3 Simulation environment . 21 4 The GNU C compiler 23 4.1 The compiler system . 23 4.1.1 The compiler parts . 24 4.2 The porting mechanisms . 25 4.2.1 The C macros: tm.h ..................... 26 4.2.2 Variable arguments . 42 4.2.3 The C file: tm.c ....................... 43 4.2.4 The machine description: md . 43 4.2.5 The building process of the compiler . 54 4.2.6 Execution of the compiler . 57 5 The CRIS port 61 5.1 Preparations . 61 5.2 The target ABI . 62 5.2.1 Fundamental types . 62 3 4 CONTENTS 5.2.2 Non-fundamental types . 63 5.2.3 Memory layout . 64 5.2.4 Parameter passing . 64 5.2.5 Register usage . 65 5.2.6 Return values . 66 5.2.7 The function stack frame . -
In Using the GNU Compiler Collection (GCC)
Using the GNU Compiler Collection For gcc version 6.1.0 (GCC) Richard M. Stallman and the GCC Developer Community Published by: GNU Press Website: http://www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 51 Franklin Street, Fifth Floor Tel 617-542-5942 Boston, MA 02110-1301 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988-2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being \Funding Free Software", the Front-Cover Texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ::::::::::::::::::::::::::::::::::::::::::::: 1 1 Programming Languages Supported by GCC ::::::::::::::: 3 2 Language Standards Supported by GCC :::::::::::::::::: 5 3 GCC Command Options ::::::::::::::::::::::::::::::: 9 4 C Implementation-Defined Behavior :::::::::::::::::::: 373 5 C++ Implementation-Defined Behavior ::::::::::::::::: 381 6 Extensions to -
Latticemico8 Development Tools User Guide
LatticeMico8 Development Tools User Guide Copyright Copyright © 2010 Lattice Semiconductor Corporation. This document may not, in whole or part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine- readable form without prior written consent from Lattice Semiconductor Corporation. Lattice Semiconductor Corporation 5555 NE Moore Court Hillsboro, OR 97124 (503) 268-8000 October 2010 Trademarks Lattice Semiconductor Corporation, L Lattice Semiconductor Corporation (logo), L (stylized), L (design), Lattice (design), LSC, CleanClock, E2CMOS, Extreme Performance, FlashBAK, FlexiClock, flexiFlash, flexiMAC, flexiPCS, FreedomChip, GAL, GDX, Generic Array Logic, HDL Explorer, IPexpress, ISP, ispATE, ispClock, ispDOWNLOAD, ispGAL, ispGDS, ispGDX, ispGDXV, ispGDX2, ispGENERATOR, ispJTAG, ispLEVER, ispLeverCORE, ispLSI, ispMACH, ispPAC, ispTRACY, ispTURBO, ispVIRTUAL MACHINE, ispVM, ispXP, ispXPGA, ispXPLD, Lattice Diamond, LatticeEC, LatticeECP, LatticeECP-DSP, LatticeECP2, LatticeECP2M, LatticeECP3, LatticeMico8, LatticeMico32, LatticeSC, LatticeSCM, LatticeXP, LatticeXP2, MACH, MachXO, MachXO2, MACO, ORCA, PAC, PAC-Designer, PAL, Performance Analyst, Platform Manager, ProcessorPM, PURESPEED, Reveal, Silicon Forest, Speedlocked, Speed Locking, SuperBIG, SuperCOOL, SuperFAST, SuperWIDE, sysCLOCK, sysCONFIG, sysDSP, sysHSI, sysI/O, sysMEM, The Simple Machine for Complex Design, TransFR, UltraMOS, and specific product designations are either registered trademarks or trademarks of Lattice Semiconductor Corporation -
System V Application Binary Interface AMD64 Architecture Processor Supplement Draft Version 0.99.4
System V Application Binary Interface AMD64 Architecture Processor Supplement Draft Version 0.99.4 Edited by Michael Matz1, Jan Hubickaˇ 2, Andreas Jaeger3, Mark Mitchell4 January 13, 2010 [email protected] [email protected] [email protected] [email protected] AMD64 ABI Draft 0.99.4 – January 13, 2010 – 15:33 Contents 1 Introduction 8 2 Software Installation 9 3 Low Level System Information 10 3.1 Machine Interface . 10 3.1.1 Processor Architecture . 10 3.1.2 Data Representation . 10 3.2 Function Calling Sequence . 14 3.2.1 Registers and the Stack Frame . 14 3.2.2 The Stack Frame . 15 3.2.3 Parameter Passing . 16 3.3 Operating System Interface . 23 3.3.1 Exception Interface . 23 3.3.2 Virtual Address Space . 23 3.3.3 Page Size . 23 3.3.4 Virtual Address Assignments . 23 3.4 Process Initialization . 26 3.4.1 Initial Stack and Register State . 26 3.4.2 Thread State . 29 3.4.3 Auxiliary Vector . 29 3.5 Coding Examples . 31 3.5.1 Architectural Constraints . 32 3.5.2 Conventions . 34 3.5.3 Position-Independent Function Prologue . 35 3.5.4 Data Objects . 36 3.5.5 Function Calls . 44 3.5.6 Branching . 46 1 AMD64 ABI Draft 0.99.4 – January 13, 2010 – 15:33 3.5.7 Variable Argument Lists . 49 3.6 DWARF Definition . 54 3.6.1 DWARF Release Number . 55 3.6.2 DWARF Register Number Mapping . 55 3.7 Stack Unwind Algorithm . 55 4 Object Files 59 4.1 ELF Header . -
Powerpc Processor Supplement
SYSTEM V APPLICATION BINARY INTERFACE PowerPC Processor Supplement by Steve Zucker, SunSoft Kari Karhi, IBM September 1995 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. Part No: 802-3334-10 Revision A, September 1995 A Sun Microsystems, Inc. Business 1995 Sun Microsystems, Inc. All rights reserved. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. 1993 IBM Corporation. All rights reserved. This specification includes material copyrighted by UNIX System Laboratories, Inc., which is reproduced with permission. TRADEMARKS Sun,Sun Microsystems, the Sun logo, SunSoft, and the SunSoft logo 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. The PowerPC and PowerPC Architecture names are trademarks of International Business Machines Corporation. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Please Recycle CONTENTS 1. INTRODUCTION 1-1 The PowerPC Processor and the System V ABI 1-1 How to Use the PowerPC Processor ABI Supplement 1-1 Evolution of the ABI Specification 1-1 2. SOFTWARE INSTALLATION 2-1 Software Distribution Formats 2-1 Physical Distribution Media 2-1 3. LOW-LEVEL SYSTEM INFORMATION 3-1 Machine Interface 3-1 Processor Architecture 3-1 Data Representation 3-1 Function -
C64 Language Reference
C64 Language Reference C64 supports an extended ‘C’ language compiler. In addition to the standard ‘C’ language C64 adds the following: run-time type identification (via typenum()) exception handling (via try/throw/catch) spinlocks (via spinlock/lockfail/spinunlock) interrupt functions multiple case constants eg. case ‘1’,’2’,’3’: inline assembler code (asm) pascal calling conventions (pascal) no calling conventions (nocall / naked) additional loop constructs (until, loop, forever) true/false are defined as 1 and 0 respectively thread storage class The following additions have been made: typenum(<type>) allow run-time type identification. It returns a hash code for the type specified. It works the same way the sizeof() operator works, but it returns a code for the type, rather than the types size. C64 supports a simple try/throw/catch mechanism. A catch statement without a variable declaration catches all exceptions. try { <statement> } catch(var decl) { } catch(var decl) { } catch { } Types: A byte is one byte (8 bits) in size. A char is two bytes (16 bits) in size. An int is eight bytes (64 bits) wide. An short int is four bytes (32 bits) wide Pointers are eight bytes (64 bits) wide. typenum() Typenum() works like the sizeof() operator, but it returns a hashcode representing the type, rather than the size of the type. Typenum() can be used to identify types at run-time. struct tag { int i; }; main() { int n; n = typenum(struct tag); } spinlock A spinlock acts to guard a section of program code against re-entry. The spinlock will block a second thread from executing a protected section of code, until the first thread is finished with it. -
VMS 4.2 Service Begins
r, University of Minnesota Twin Cities May 1986 VAX News VMS 4.2 Service Begins Marisa Riviere On April16 the VAX 8600, ACSS's passwords on the VAX 8600 are network prompt as described new VX system, became available the same as those you were using above. to our users. This larger, faster on the VAX 11/780 at the time of VAX permits us to offer new VMS the transfer. You may also have to change your services that were difficult or terminal parity; in VMS 4.2 the impossible to offer on the VA, a As previously announced in our parity default is even. smaller VMS machine, and will cost March Newsletter, we discontinued users 20 to 30 percent less than our VMS 3.6 service on the VA a the VA. few days after the VX became Training Software available. The ACSS additions to the VMS We plan to offer several on-line operating system have been Not all the software available on the training packages on the VX. As transferred to the VAX 8600. VAX 11/780 was transferred to the we go to press, two packages are There are, however, some VAX 8600. See the March available: the Introduction to VMS important differences between Newsletterorthe VMS42 writeup and the Introduction to EDT. (EDT VMS 4.2 (the operating system on on the VX for details. is the VMS line and full-screen the VX) and VMS 3.6 (the editor). To use e~her package, first operating system on the VA). type in the set term/vt100 Some changes are discussed later Logging On command.