DOCSLIB.ORG

Compiling for Resource-Constrained Platforms Using Asshes: Application- and System-Specific Heuristics

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Compiling for Resource-Constrained Platforms Using Asshes: Application- and System-Specific Heuristics Compiling for Resource-Constrained Platforms using ASSHes: Application- and System-Specific Heuristics Alastair Reid Nathan Cooprider John Regehr School of Computing, University of Utah Unpublished draft — November 2004 ABSTRACT tem. Instead of creating fast and not-too-big code, the compiler We present and evaluate application- and system-specific heuristics should aggressively try to generate code that fits into the available (ASSHes) for optimizing embedded software. ASSHes are scripts code and data space. Furthermore, the compiler should expend ex- that decide which compiler optimizations to apply; they make deci- tra optimization effort on tasks with real-time requirements. sions using feedback from previous compilations, using the results Developers using current tools can affect optimization heuristics of program analyses, and using high-level information, e.g., “there in various ways that are coarse-grained (e.g., global optimization are only 4 KB of RAM, and interrupt handlers 5–7 should be fast flags) and fine grained (e.g., profile data, pragmas). In general since we expect them to execute very frequently.” In contrast, tradi- this control is insufficient for meeting complex application- and tional compilers base optimization decisions on built-in heuristics platform-specific goals that involve multiple resources. There are that are oblivious to high-level application- and platform-specific two fundamental problems with existing tools: concerns. The ASSH effectively becomes the high-level optimiza- 1. Compilers are oblivious to the high-level non-functional re- tion policy and the existing compiler becomes a low-level mecha- quirements that are externally imposed on an embedded sys- nism for applying code transformations. ASSHes are more generic tem. than previous approaches to compiling embedded software: they permit compilation to be directed towards meeting many different 2. Compilers rely on a multitude of built-in heuristics for de- goals and combinations of goals. ciding when to apply optimizations that are not universally So far we have investigated ASSHes that control two optimiza- beneficial. It is difficult to gain effective overall control over tions: loop unrolling and function inlining. We evaluate ASSHes a diverse collection of opaque heuristics. by applying them to TinyOS sensor network applications, where they have successfully reduced resource usage. For example, for Lacking compiler support for meeting high-level resource con- one large application we can either reduce worst-case stack depth straints, developers are forced to manually specialize code to tune by 16%, reduce code size by 3.5%, or reduce the amount of time the resource usage. Manual specialization is harmful because it is time- processor is active by 14% (our baseline for comparison is the out- consuming and can introduce bugs. Also, it discourages reuse: the put of the nesC compiler, which itself performs aggressive cross- resulting code often sacrifices modularity and, furthermore, it is module inlining). These various improvements conflict: they can fragile with respect to changes in the underlying hardware plat- be achieved individually but not together—dealing with tradeoffs form: today’s resource constraints are not necessarily tomorrow’s. among resources is central to designing efficient embedded sys- This paper proposes a way to make existing compilers more suit- tems. able for compiling embedded software: we use application- and system-specific heuristics (ASSHes) to override optimization de- cisions made by the compiler. ASSHes have access to high-level 1. INTRODUCTION system requirements and to external program analyzers, code in- Optimizing compilers try to generate code that is fast and not too strumentation techniques, feedback mechanisms, etc. to direct their large—an appropriate design point for desktop and workstation ap- choices. Particularly important is giving ASSHes access to re- plications. Embedded software developers, on the other hand, are source bounding analyses [2, 21] that can statically determine if often not well-served by these compilers: their software must run a program will, for example, dynamically run out of memory. In on platforms with diverse and severe non-functional requirements. effect, the ASSH becomes the high-level optimization policy while For example, consider a program that will be run on a processor the existing compiler becomes the low-level mechanism for apply- with a low clock speed, limited battery energy, and little space for ing code transformations. This mechanism/policy separation is cru- code and data—in other words, a typical low-power embedded sys- cial: ASSHes present developers with a very narrow interface to the compiler, giving them the capability to extend it in a constrained way. In contrast, a generally extensible compiler is more power- ful but exports a much wider interface, for example exposing the compiler’s intermediate representations. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are The benefits of ASSHes come not from including any particular not made or distributed for profit or commercial advantage and that copies analyzer or heuristic—after all, compiler writers could equally well bear this notice and the full citation on the first page. To copy otherwise, to include that analyzer or heuristic—but from the ease with which republish, to post on servers or to redistribute to lists, requires prior specific new ASSHes can be written or combined. This is a corollary to permission and/or a fee. Robison’s observation [23] that Copyright 2004 ACM X-XXXXX-XX-X/XX/XX ...$5.00. 1 . small programming niches that would greatly ben- 32 Size-driven ASSH efit from certain optimizations cannot get those opti- 30 Bloat-driven ASSH mizations implemented, because payback for the com- piler vendor is not there. 28 26 Robison was not talking about the embedded domain but his obser- vation is particularly applicable there. The large diversity of archi- 24 nesC tectures, compilers, and operating systems for embedded systems Code size (KB) 22 best produces a high degree of market fragmentation. This fragmenta- 20 tion, in combination with the diverse non-functional requirements 18 imposed on embedded systems, guarantees the existence of many 0 20 40 60 80 100 small niches whose needs are not met by off-the-shelf tools. Percentage of functions inlined The contributions of this paper are: • We describe ASSHes: a novel organization for extensible op- Figure 1: Code size for the Surge Reliable application us- timization heuristics that exploits existing optimization passes ing two simple ASSHes, nesC, and our best heuristic. in order to meet application- and platform-specific goals. We intend ASSHes to be developed by programmers with a basic understanding of compilers and compiler optimizations—not • ASSHes can easily be made aware of high-level platform- by compiler specialists. and application-specific requirements, • We show that ASSHes are effective: we present experimen- • multiple ASSHes can be composed to support more sophis- tal results showing that they can produce code substantially ticated optimizations, and better than that produced by competing techniques. For ex- • ASSHes provide a convenient platform for making use of ample, on a large example we can reduce stack memory con- feedback to improve generated code. sumption by 16% or we can reduce the amount of time that the processor is active (and using energy) by 14%. 2.1 Background: TinyOS and nesC • We show that ASSHes are general: they support a variety of TinyOS is extremely lightweight systems software for the Berke- underlying optimizations (in this paper we describe ASSHes ley mote sensor network platform [10]. Motes are microcontroller- that utilize loop unrolling and function inlining) and they per- based embedded systems equipped with sensors and a packet radio. mit a wide variety of high-level goals to be met. ASSHes can The need to conserve energy and reduce costs imposes severe re- also be composed to meet more complex goals. source constraints: the mica2 motes that we use as an experimental platform are based on Atmel’s ATmega128 chip running at about • We show that ASSHes are practical: they can be added to 7 MHz. The Atmel chip implements the 8-bit AVR architecture. an existing compiler such as gcc either by modifying its code It has 128 KB of flash memory for storing programs and 4 KB of in minor ways, or by preprocessing its input using a source- RAM for data. to-source transformer. The nesC language [8] addresses the particular requirements of the mote platform by providing static component linking, whole- ASSHes significantly generalize our previous work on reducing program optimization through inlining, and static detection of con- stack depth [21], which considered tradeoffs between stack mem- currency errors. The nesC compiler emits C that is fed to a gcc ory and code memory. cross-compiler for AVR. Throughout this paper, our baseline for Section 2 provides a concrete introduction to application- and comparison is provided by the binaries generated by nesC and gcc. system-specific heuristics for optimizing embedded software by The Surge Reliable application, developed at Crossbow Inc., using a variety of ASSHes to optimize a nesC/TinyOS program. is the motivating application for this section. It performs multihop In Section 3 we describe the use of aggressive feedback-driven routing of sensor data to a sink node. Surge Reliable is rela- ASSHes to better compile embedded software. Section 4 describes tively large: it uses code from 43 components and, when compiled the interface between ASSHes and the compiler, and how to mod- by nesC, generates about 15,700 lines of C code in about 500 func- ify compilers to support ASSHes. In Section 5 we evaluate the tions. effectiveness of several ASSHes in reducing resource usage of a number of TinyOS applications that run on Berkeley motes [10]. 2.2 Code-size-driven ASSHes We compare ASSHes to previous work in Section 6 and conclude Our first example uses a variety of heuristics to achieve code-size in Section 7.
Load more

Recommended publications
  • Riscv-Software-Stack-Tutorial-Hpca2015
    Software Tools Bootcamp RISC-V ISA Tutorial — HPCA-21 08 February 2015 Albert Ou UC Berkeley [email protected] Preliminaries To follow along, download these slides at http://riscv.org/tutorial-hpca2015.html 2 Preliminaries . Shell commands are prefixed by a “$” prompt. Due to time constraints, we will not be building everything from source in real-time. - Binaries have been prepared for you in the VM image. - Detailed build steps are documented here for completeness but are not necessary if using the VM. Interactive portions of this tutorial are denoted with: $ echo 'Hello world' . Also as a reminder, these slides are marked with an icon in the upper-right corner: 3 Software Stack . Many possible combinations (and growing) . But here we will focus on the most common workflows for RISC-V software development 4 Agenda 1. riscv-tools infrastructure 2. First Steps 3. Spike + Proxy Kernel 4. QEMU + Linux 5. Advanced Cross-Compiling 6. Yocto/OpenEmbedded 5 riscv-tools — Overview “Meta-repository” with Git submodules for every stable component of the RISC-V software toolchain Submodule Contents riscv-fesvr RISC-V Frontend Server riscv-isa-sim Functional ISA simulator (“Spike”) riscv-qemu Higher-performance ISA simulator riscv-gnu-toolchain binutils, gcc, newlib, glibc, Linux UAPI headers riscv-llvm LLVM, riscv-clang submodule riscv-pk RISC-V Proxy Kernel (riscv-linux) Linux/RISC-V kernel port riscv-tests ISA assembly tests, benchmark suite All listed submodules are hosted under the riscv GitHub organization: https://github.com/riscv 6 riscv-tools — Installation . Build riscv-gnu-toolchain (riscv*-*-elf / newlib target), riscv-fesvr, riscv-isa-sim, and riscv-pk: (pre-installed in VM) $ git clone https://github.com/riscv/riscv-tools $ cd riscv-tools $ git submodule update --init --recursive $ export RISCV=<installation path> $ export PATH=${PATH}:${RISCV}/bin $ ./build.sh .
    [Show full text]
  • Operating Systems and Applications for Embedded Systems >>> Toolchains
    >>> Operating Systems And Applications For Embedded Systems >>> Toolchains Name: Mariusz Naumowicz Date: 31 sierpnia 2018 [~]$ _ [1/19] >>> Plan 1. Toolchain Toolchain Main component of GNU toolchain C library Finding a toolchain 2. crosstool-NG crosstool-NG Installing Anatomy of a toolchain Information about cross-compiler Configruation Most interesting features Sysroot Other tools POSIX functions AP [~]$ _ [2/19] >>> Toolchain A toolchain is the set of tools that compiles source code into executables that can run on your target device, and includes a compiler, a linker, and run-time libraries. [1. Toolchain]$ _ [3/19] >>> Main component of GNU toolchain * Binutils: A set of binary utilities including the assembler, and the linker, ld. It is available at http://www.gnu.org/software/binutils/. * GNU Compiler Collection (GCC): These are the compilers for C and other languages which, depending on the version of GCC, include C++, Objective-C, Objective-C++, Java, Fortran, Ada, and Go. They all use a common back-end which produces assembler code which is fed to the GNU assembler. It is available at http://gcc.gnu.org/. * C library: A standardized API based on the POSIX specification which is the principle interface to the operating system kernel from applications. There are several C libraries to consider, see the following section. [1. Toolchain]$ _ [4/19] >>> C library * glibc: Available at http://www.gnu.org/software/libc. It is the standard GNU C library. It is big and, until recently, not very configurable, but it is the most complete implementation of the POSIX API. * eglibc: Available at http://www.eglibc.org/home.
    [Show full text]
  • Linux Journal | February 2016 | Issue
    ™ A LOOK AT KDE’s KStars Astronomy Program Since 1994: The Original Magazine of the Linux Community FEBRUARY 2016 | ISSUE 262 | www.linuxjournal.com + Programming Working with Command How-Tos Arguments in Your Program a Shell Scripts BeagleBone Interview: Katerina Black Barone-Adesi on to Help Brew Beer Developing the Snabb Switch Network Write a Toolkit Short Script to Solve a WATCH: ISSUE Math Puzzle OVERVIEW V LJ262-February2016.indd 1 1/21/16 5:26 PM NEW! Agile Improve Product Business Development Processes with an Enterprise Practical books Author: Ted Schmidt Job Scheduler for the most technical Sponsor: IBM Author: Mike Diehl Sponsor: people on the planet. Skybot Finding Your DIY Way: Mapping Commerce Site Your Network Author: to Improve Reuven M. Lerner Manageability GEEK GUIDES Sponsor: GeoTrust Author: Bill Childers Sponsor: InterMapper Combating Get in the Infrastructure Fast Lane Sprawl with NVMe Author: Author: Bill Childers Mike Diehl Sponsor: Sponsor: Puppet Labs Silicon Mechanics & Intel Download books for free with a Take Control Linux in simple one-time registration. of Growing the Time Redis NoSQL of Malware http://geekguide.linuxjournal.com Server Clusters Author: Author: Federico Kereki Reuven M. Lerner Sponsor: Sponsor: IBM Bit9 + Carbon Black LJ262-February2016.indd 2 1/21/16 5:26 PM NEW! Agile Improve Product Business Development Processes with an Enterprise Practical books Author: Ted Schmidt Job Scheduler for the most technical Sponsor: IBM Author: Mike Diehl Sponsor: people on the planet. Skybot Finding Your DIY Way: Mapping Commerce Site Your Network Author: to Improve Reuven M. Lerner Manageability GEEK GUIDES Sponsor: GeoTrust Author: Bill Childers Sponsor: InterMapper Combating Get in the Infrastructure Fast Lane Sprawl with NVMe Author: Author: Bill Childers Mike Diehl Sponsor: Sponsor: Puppet Labs Silicon Mechanics & Intel Download books for free with a Take Control Linux in simple one-time registration.
    [Show full text]
  • Compiler Construction
    Compiler Construction Chapter 11 Compiler Construction Compiler Construction 1 A New Compiler • Perhaps a new source language • Perhaps a new target for an existing compiler • Perhaps both Compiler Construction Compiler Construction 2 Source Language • Larger, more complex languages generally require larger, more complex compilers • Is the source language expected to evolve? – E.g., Java 1.0 ! Java 1.1 ! . – A brand new language may undergo considerable change early on – A small working prototype may be in order – Compiler writers must anticipate some amount of change and their design must therefore be flexible – Lexer and parser generators (like Lex and Yacc) are therefore better than hand- coding the lexer and parser when change is inevitable Compiler Construction Compiler Construction 3 Target Language • The nature of the target language and run-time environment influence compiler construction considerably • A new processor and/or its assembler may be buggy Buggy targets make it difficult to debug compilers for that target! • A successful source language will persist over several target generations – E.g., 386 ! 486 ! Pentium ! . – Thus the design of the IR is important – Modularization of machine-specific details is also important Compiler Construction Compiler Construction 4 Compiler Performance Issues • Compiler speed • Generated code quality • Error diagnostics • Portability • Maintainability Compiler Construction Compiler Construction 5 Compiler Speed • Reduce the number of modules • Reduce the number of passes Perhaps generate machine
    [Show full text]
  • A Model-Driven Development and Verification Approach
    A MODEL-DRIVEN DEVELOPMENT AND VERIFICATION APPROACH FOR MEDICAL DEVICES by Jakub Jedryszek B.S., Wroclaw University of Technology, Poland, 2012 B.A., Wroclaw University of Economics, Poland, 2012 A THESIS submitted in partial fulfillment of the requirements for the degree MASTER OF SCIENCE Department of Computing and Information Sciences College of Engineering KANSAS STATE UNIVERSITY Manhattan, Kansas 2014 Approved by: Major Professor John Hatcliff Abstract Medical devices are safety-critical systems whose failure may put human life in danger. They are becoming more advanced and thus more complex. This leads to bigger and more complicated code-bases that are hard to maintain and verify. Model-driven development provides high-level and abstract description of the system in the form of models that omit details, which are not relevant during the design phase. This allows for certain types of verification and hazard analysis to be performed on the models. These models can then be translated into code. However, errors that do not exist in the models may be introduced during the implementation phase. Automated translation from verified models to code may prevent to some extent. This thesis proposes approach for model-driven development and verification of medi- cal devices. Models are created in AADL (Architecture Analysis & Design Language), a language for software and hardware architecture modeling. AADL models are translated to SPARK Ada, contract-based programming language, which is suitable for software veri- fication. Generated code base is further extended by developers to implement internals of specific devices. Created programs can be verified using SPARK tools. A PCA (Patient Controlled Analgesia) pump medical device is used to illustrate the primary artifacts and process steps.
    [Show full text]
  • Linux Everywhere a Look at Linux Outside the World of Desktops
    Linux Everywhere A look at Linux outside the world of desktops CIS 191 Spring 2012 – Guest Lecture by Philip Peng Lecture Outline 1. Introduction 2. Different Platforms 3. Reasons for Linux 4. Cross-compiling 5. Case Study: iPodLinux 6. Questions 2 What’s in common? 3 All your hardware are belong to us • Linux is everywhere – If its programmable, you can put Linux on it! – Yes, even a microwave CES 2010, microwave running Android: http://www.handlewithlinux.com/linux-washing-cooking 4 Servers • What servers use – Stability, security, free – Examples: ◦ CentOS ◦ Debian ◦ Red Hat 5 Desktop • What you use – Free Windows/Mac alternative – Examples: ◦ Ubuntu ◦ Fedora ◦ PCLinuxOS 6 Gaming Devices • What (white-hat) hackers do – To run “homebrew” software – Examples: ◦ PS3, Wii, XBOX ◦ PS2, GameCube ◦ Dreamcast ◦ PSP, DS ◦ Open Pandora, GP2X 7 Mobile Devices • What distributors are developing – Community contribution – Examples ◦ Android ◦ Maemo/MeeGo/Tizen ◦ Openmoko 8 Embedded Devices • What embedded hardware run – Small footprint, dev tools – Examples ◦ RTLinux (real-time) ◦ μClinux (no MMU) ◦ Ångström (everything) 9 Why? 10 Free! • Free! – As in freedom, i.e. open source – As in beer, i.e. vs paid upgrades 11 Homebrew! • Run own software – Your hardware your software? 12 Support! • Community contribution – “For the greater good” (i.e. users) – Everyone contributes ◦ Specialists from all over the world – Existing hardware support ◦ Many already supported computer architecture ◦ Modify existing drivers 13 Lots of support! 14 Why not? • Because we can – If its hackable, it can run Linux 15 How? • How do we get Linux running on XXX? • Port: A version of software modified to run on a different target platform – The PS3 port of Fedora is a modified build of Fedora compiled to run on the PS3 architecture – e.g.
    [Show full text]
  • Embedded Linux Device Driver Development Sébastien Bilavarn
    Embedded Linux Device driver development Sébastien Bilavarn Polytech’Nice Sophia - Département Electronique - Université de Nice Sophia Antipolis - S. Bilavarn - 1 - Outline Ch1 – Introduction to Linux Ch2 – Linux kernel overview Ch3 – Linux for Embedded Systems Ch4 – Embedded Linux distributions Ch5 – Case study: Xilinx PowerPC Linux Ch5 bis – Case study: Xilinx Zynq-7000 Linux Ch6 – Device driver development Polytech’Nice Sophia - Département Electronique - Université de Nice Sophia Antipolis - S. Bilavarn - 2 - Linux for Embedded Systems Introduction to Embedded Linux Key features Embedded Linux development Linux kernel development Polytech’Nice Sophia - Département Electronique - Université de Nice Sophia Antipolis - S. Bilavarn - 3 - Embedded Linux What is Embedded Linux ? Strictly speaking Embedded Linux is an operating system based on Linux and adapted specifically to the constraints of embedded systems. Unlike standard versions of Linux for Personal Computers, embedded Linux is designed for systems with limited resources Memory: few RAM, sometimes no Memory Management Unit (MMU) Storage: Flash instead of hard disk drive Since embedded systems are often designed for domain specific purposes and specific target platforms, they use kernel versions that are optimized for a given context of application. This results in different Linux kernel variants that are also called Linux distributions Polytech’Nice Sophia - Département Electronique - Université de Nice Sophia Antipolis - S. Bilavarn - 4 - Embedded Linux What is embedded Linux ? Embedded Linux is used in embedded systems such as mobile phones, personal digital assistants (PDA), media players set-top boxes, and other consumer electronics devices networking equipment machine control, industrial automation navigation equipment medical instruments Key features runs in a small embedded system, typically booting out of Flash, no hard disk drive, no full-size video display, and take far less than 2 minutes to boot up, sometimes supports real- time tasks.
    [Show full text]
  • Cross-Compiler Bipartite Vulnerability Search
    electronics Article Cross-Compiler Bipartite Vulnerability Search Paul Black * and Iqbal Gondal Internet Commerce Security Laboratory (ICSL), Federation University, Ballarat 3353, Australia; [email protected] * Correspondence: [email protected] Abstract: Open-source libraries are widely used in software development, and the functions from these libraries may contain security vulnerabilities that can provide gateways for attackers. This paper provides a function similarity technique to identify vulnerable functions in compiled programs and proposes a new technique called Cross-Compiler Bipartite Vulnerability Search (CCBVS). CCBVS uses a novel training process, and bipartite matching to filter SVM model false positives to improve the quality of similar function identification. This research uses debug symbols in programs compiled from open-source software products to generate the ground truth. This automatic extraction of ground truth allows experimentation with a wide range of programs. The results presented in the paper show that an SVM model trained on a wide variety of programs compiled for Windows and Linux, x86 and Intel 64 architectures can be used to predict function similarity and that the use of bipartite matching substantially improves the function similarity matching performance. Keywords: malware similarity; function similarity; binary similarity; machine-learning; bipar- tite matching 1. Introduction Citation: Black, P.; Gondal, I. Cross-Compiler Bipartite Function similarity techniques are used in the following activities, the triage of mal- Vulnerability Search. Electronics 2021, ware [1], analysis of program patches [2], identification of library functions [3], analysis of 10, 1356. https://doi.org/10.3390/ code authorship [4], the identification of similar function pairs to reduce manual analysis electronics10111356 workload, [5], plagiarism analysis [6], and for vulnerable function identification [7–9].
    [Show full text]
  • COSMIC C Cross Compiler for Stmicroelectronics ST7 Family
    COSMIC C Cross Compiler for STMicroelectronics ST7 Family COSMIC’s C cross compiler, cxST7 for the STMicroelectronics ST7 family of microcontrollers, incorporates over fifteen years of innovative design and development effort. Used in the field since 1997, cxST7 is reliable, field-proven, and incorporates many features to help ensure your embedded ST7 design meets and exceeds performance specifications. The C Compiler package for Windows includes: COSMIC integrated development environment (IDEA), optimizing C cross compiler, macro assembler, linker, librarian, object inspector, hex file generator, object format converters, debugging support utilities, run-time libraries and a compiler command driver. The PC compiler package runs under Windows 95/98/ME/NT4/2000 and XP.. Key Features Microcontroller-Specific Design Supports All ST7 Family Microcontrollers cxST7, is designed specifically for the STMicroelectronics ST7 family of microcontrollers; all ST7 family processors are ANSI C Implementation supported. A special code generator and optimizer targeted for the ST7 family eliminates the overhead and complexity of Extensions to ANSI for Embedded Systems a more generic compiler. You also get header file support for Global and Processor-Specific Optimizations many of the popular ST7 peripherals, so you can access their memory mapped objects by name either at the C or assembly Optimized Function Calling language levels. Debug Fully Optimized Code ANSI / ISO Standard C Automatic Checksums This implementation conforms with the ANSI and ISO Real and Simulated Stack models Standard C syntax specifications which helps you protect Smart Linker optimizes RAM usage your software investment by aiding code portability and reliability. C support for Zero Page Data C support for Interrupt Handlers Flexible User Interface The Cosmic C compiler can be used with the included Three In-Line Assembly Methods Windows IDEA or as a Windows 32-bit command line Assembler Supports C #defines and #includes application for use with your favorite editor, make or source code control system.
    [Show full text]
  • GNAT User's Guide
    GNAT User's Guide GNAT, The GNU Ada Compiler For gcc version 4.7.4 (GCC) AdaCore Copyright c 1995-2009 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 no Invariant Sections, with no Front-Cover Texts and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". About This Guide 1 About This Guide This guide describes the use of GNAT, a compiler and software development toolset for the full Ada programming language. It documents the features of the compiler and tools, and explains how to use them to build Ada applications. GNAT implements Ada 95 and Ada 2005, and it may also be invoked in Ada 83 compat- ibility mode. By default, GNAT assumes Ada 2005, but you can override with a compiler switch (see Section 3.2.9 [Compiling Different Versions of Ada], page 78) to explicitly specify the language version. Throughout this manual, references to \Ada" without a year suffix apply to both the Ada 95 and Ada 2005 versions of the language. What This Guide Contains This guide contains the following chapters: • Chapter 1 [Getting Started with GNAT], page 5, describes how to get started compiling and running Ada programs with the GNAT Ada programming environment. • Chapter 2 [The GNAT Compilation Model], page 13, describes the compilation model used by GNAT. • Chapter 3 [Compiling Using gcc], page 41, describes how to compile Ada programs with gcc, the Ada compiler.
    [Show full text]
  • Motorola 68000 Family C Cross Compiler Notice
    User’s Guide HP B3640 Motorola 68000 Family C Cross Compiler Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. © Copyright 1987-1994, Hewlett-Packard Company. This document contains proprietary information, which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice. UNIX is a registered trademark of UNIX System Laboratories Inc. in the U.S.A. and other countries. MS-DOS and Windows are U.S. registered trademarks of Microsoft Corporation. Hewlett-Packard Company P.O . Box 2197 1900 Garden of the Gods Road Colorado Springs, CO 80901-2197, U.S.A. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subparagraph (C) (1) (ii) of the Rights in Technical Data and Computer Software Clause in DFARS 252.227-7013. Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, CA 94304 U.S.A. Rights for non-DOD U.S. Government Departments and Agencies are set forth in FAR 52.227-19(c)(1,2).
    [Show full text]
  • The GNU Toolchain for ARM Targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb
    This chapter contains information on building a GNU toolchain for ARM targets. The GNU Toolchain for ARM targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb This document contains information on setting up a GNU toolchain for ARM targets. It details both some pre-compiled toolchains which you can install, and how to compile your own toolchain, as either a native or a cross-compiler. 1. Credits This document is based on the work of Chris Rutter (now, sadly, deceased) who’s ’Building the GNU toolchain for ARM targets’ document was gospel for some time. It eventually became out of date so Wookey (<[email protected]>) updated it and gave it a substantion rewrite, adding the pre-built toolchain info at the same time. Paul Webb (<[email protected]>) did the initial conversion to DocBook, Phil 1 The GNU Toolchain for ARM targets HOWTO Blundell (<[email protected]>) provided info on the current state of the art and comments on the draft. Jeff Sutherland (<[email protected]>) then fixed the bits that were still wrong, and now maintains the doc, along with Wookey. Thanx to all. As well as being on-line as a stand-alone HOWTO, this document is also available as a chapter of the book: A ’Guide to ARMLinux for Developers’ (http://www.aleph1.co.uk/armlinux/thebook.html) 2 This chapter contains information on building a GNU toolchain for ARM targets. 1. Toolchain overview The toolchain actually consists of a number of components. The main one is the compiler itself gcc, which can be native to the host or a cross-compiler.
    [Show full text]