DOCSLIB.ORG

Contract-Based Programming on Modern C++

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Contract-Based Programming on Modern C++ Universidad Carlos III de Madrid Escuela Politécnica Superior Bachelor Degree in Computer Engineering Bachelor Thesis Contract-Based Programming on Modern C++ Author: José Cabrero Holgueras Supervisor: José Daniel García Sánchez Leganés, Madrid, Spain July 2018 “Mentors are there in the moments of truth” Anonymous iv Contract-Based Programming on the Modern C++ Acknowledgements There are so many people who have been involved in the development of this project. First of all, I would like to thank all my family for all their support and unconditional help, especially over this last year. I could not have borne the load if you would not have been present with all this help. There are not enough lines in this document to thank what you have given me. I want to especially thank Javier López. I did not think I would live to know a genius, but I did. He has computer science in his veins and transmits his passion to anyone close to him. It is astonishing what he can do with a computer. He has taught me everything he knew when I needed and helped me like no one has in this work. A real mentor is the one that sits next to you and guides you in solving your problems, and Javier has been mine. There is probably no one in the group as dedicated to its task as Javier is. I wish I had had more time to share with him since it has been a real inspiration for this work. If someone deserves credit in the ideas of this project, it is Javier who does. I would also like to give a huge thank to Manuel F. Dolz. You also contributed to this project offering me to work with you. When I received the offer, I did not think I would earn what I have. It has been an incredible experience. If I look back to September, I was a completely different person, and things that change you, are what define who you are. I am specially thankful to David del Rio, to Javier Fernandez and to Mario Vasile, because they were present on the last days of this project. Each of them has given something to this project that makes it unique and without their collaboration, this project would not have been what it is. I do not really imagine how this would have ended up without your collaboration. Thank you. My labmates also deserve some words here. They have been my classmates, my friends and my partners during this journey that has been the degree. Thanks to Laura Martín for helping me in those desperation moments in the lab, you really helped me out. And thanks to Nerea Luna for all those train travels back and forth, your support during all these years is immeasurable. Thanks for talking to me on stress moments and for always believing in me. v Thanks to Saúl Alonso, because he has always guided me and telling me about any opportunities that there are out there; to Javier Prieto, who has cared of me from the very first moment that I joined the group. He has always been there and it has been an inspiration to follow what I really liked to do, and his support at all points. And to Guillermo Izquierdo, who helped me a lot on the decision of the Master Course and I really believe that thanks to that, I will follow my dream. Thanks to you all, you have all given me something that I will always keep, and you have all been an inspiration for me to be better. Thanks to Ignacio Guillermo Martínez and to Alejandro Rey. They have been my classmates and I could not imagine a better group of friends. Thanks to all the work you put up to help me with practices and for those good moments we spent. Finally, thanks José Daniel García and the ARCOS group for offering me a job in the department and lending me all the equipment and tools that I needed. This project has been more than a learning process, it has been a personal growth. Thanks to all of you. Contract-Based Programming on Modern C++ Bachelor Thesis José Cabrero Holgueras Abstract Contract-based Programming or Design By Contract (DBC) is a discipline for system construction that in recent years has postulated to be one of the most solid and reliable models for software creation. It is well known that in the software industry the number of projects not being successfully developed is huge. The main cause of the failure is that projects do not meet user expectations. In this context, Design By Contract seems to emerge as a solution to decrease this failure rate. This philosophy provides a set of mechanisms for the validation of part of the requirements specification. In recent years, several programming languages started to implement DBC, either as part of the lan- guage or an external library. The main programming languages that support contract-based program- ming are Ada 2012, Spark, Eiffel, D, C# CodeContracts or Microsoft Source-Code Annotation Language (Microsoft SAL). Traditionally, C++ has been a programming language focused on flexibility, perfor- mance and efficiency. This has attracted many people to carry out projects using this programming language. However, trends make programming languages change, and the interests of the industry are leaning towards solid solutions. Those solutions shall include frameworks that are reliable. With this same purpose, C++ has designed a specification for the implementation of Design By Contract in the programming language. This new specification has been accepted by the ISO C++ committee to be included in C++20. The specification includes several clauses that allow the user to write pre/post- conditions on the code. This allows part of the requirement specification to be merged into the code, enabling traceability between the phases of the software project. The specification of a new feature in a programming language implies changes in how the language is understood by a compiler. For the implementation of a new specification, several changes are required at different levels. This document describes these changes. Additionally, it provides an overview of the structure of a compiler, and a brief description of all the parts of the Clang C++ compiler. Keywords: · Contract Based Programming · Contract · C++ · Clang · Compiler vii Programación basada en Contratos en el C++ moderno Trabajo Fin de Grado José Cabrero Holgueras Resumen La programación por contratos es una disciplina de construcción de sistemas que recientemente se ha postulado como una de las más solidas y fiables para la creación de sistemas software. Se sabe que la industria de desarrollo de software no está siendo exitosa debido en parte a la tasa de fallos que hay en éstos. En este contexto, la programación por contratos emerge como una solución para reducir esta tasa de fracaso en la industria. Esta tendencia de desarrollo provee a los usuarios con mecanismos para la validación de los requisitos. En los últimos años, varios lenguajes de programación han comenzado a implementar la programación por contratos, bien como parte del lenguaje o como una biblioteca externa. Los principales lenguajes de programación que a día de hoy soportan programación por contratos son Ada 2012, Spark, Eiffel, D, C# CodeContracts or Microsoft Source-Code Annotation Language (Microsoft SAL). Tradicionalmente, C++ ha sido un lenguage de programación centrado en proveer al usuario con flexibilidad, rendimiento y eficiencia. Estas características han atraido a muchos clientes de cara a utilizar este lenguaje de progra- mación en proyectos. Sin embargo, las tendencías fuerzan cambios en los lenguajes de programación, y los intereses de las empresas actualmente se están inclinando hacia soluciones robustas. Estas soluciones, deben incluir marcos de trabajo que sean fiables. Con esto en mente, se ha diseñado una especificación para la programación por contratos en el lenguaje de programación. Esta nueva especificación, ha sido aceptada para por el Comite ISO C++ para ser incluida en C++20. Esta especificación provee al usuario con varios mecanismos que permiten verificar condiciones en el código. Esto permite directamente en- lazar la especificación de requisitos con la implementación de los mismos. La especificación de una nueva característica dentro de un lenguaje de programación implica cambios en como el lenguaje es entendido por un compilador. Para la implementación de estos nuevos requi- sitos se requiere de realizar modificaciones en el compilador en distintos niveles de análisis. En este proyecto, se describe un resumen de los cambios que son necesarios dentro de un compilador. Estos cambios incluyen un resumen de la estructura del compilador, posteriormente se desglosa la estructura del compilador de C++ Clang y por último se describen las modificaciones en cada una de las partes involucradas. Keywords: · Programación Basada en Contratos · Contratos · C++ · Clang · Compilador ix Contents Acknowledgments v Abstract vii Resumen ix List of Figures xviii List of Tables xxii 1 Introduction 1 1.1 Background . .1 1.2 Objectives . .2 1.3 Document Structure . .2 2 State of the Art 5 2.1 Eiffel . .5 2.1.1 Design By Contract in Eiffel . .7 2.1.2 Advantages and Disadvantages of Eiffel . .8 2.2 Ada 2012 . 10 2.2.1 Design By Contract in Ada 2012 . 11 2.2.2 Advantages and Disadvantages of Ada 2012 . 13 2.3 Spark . 15 2.3.1 Design By Contract in Spark . 16 2.3.2 Advantages and Disadvantages of Spark . 18 2.4 C# - CodeContracts . 19 2.4.1 Design By Contract in C# - Code Contracts . 20 2.4.2 Advantages and Disadvantages of C# - Code Contracts . 21 2.5 D Programming Language . 22 2.5.1 Design by Contract in D .
Load more

Recommended publications
  • What Is LLVM? and a Status Update
    What is LLVM? And a Status Update. Approved for public release Hal Finkel Leadership Computing Facility Argonne National Laboratory Clang, LLVM, etc. ✔ LLVM is a liberally-licensed(*) infrastructure for creating compilers, other toolchain components, and JIT compilation engines. ✔ Clang is a modern C++ frontend for LLVM ✔ LLVM and Clang will play significant roles in exascale computing systems! (*) Now under the Apache 2 license with the LLVM Exception LLVM/Clang is both a research platform and a production-quality compiler. 2 A role in exascale? Current/Future HPC vendors are already involved (plus many others)... Apple + Google Intel (Many millions invested annually) + many others (Qualcomm, Sony, Microsoft, Facebook, Ericcson, etc.) ARM LLVM IBM Cray NVIDIA (and PGI) Academia, Labs, etc. AMD 3 What is LLVM: LLVM is a multi-architecture infrastructure for constructing compilers and other toolchain components. LLVM is not a “low-level virtual machine”! LLVM IR Architecture-independent simplification Architecture-aware optimization (e.g. vectorization) Assembly printing, binary generation, or JIT execution Backends (Type legalization, instruction selection, register allocation, etc.) 4 What is Clang: LLVM IR Clang is a C++ frontend for LLVM... Code generation Parsing and C++ Source semantic analysis (C++14, C11, etc.) Static analysis ● For basic compilation, Clang works just like gcc – using clang instead of gcc, or clang++ instead of g++, in your makefile will likely “just work.” ● Clang has a scalable LTO, check out: https://clang.llvm.org/docs/ThinLTO.html 5 The core LLVM compiler-infrastructure components are one of the subprojects in the LLVM project. These components are also referred to as “LLVM.” 6 What About Flang? ● Started as a collaboration between DOE and NVIDIA/PGI.
    [Show full text]
  • A DSL for Resource Checking Using Finite State Automaton-Driven Symbolic Execution Code
    Open Comput. Sci. 2021; 11:107–115 Research Article Endre Fülöp and Norbert Pataki* A DSL for Resource Checking Using Finite State Automaton-Driven Symbolic Execution https://doi.org/10.1515/comp-2020-0120 code. Compilers validate the syntactic elements, referred Received Mar 31, 2020; accepted May 28, 2020 variables, called functions to name a few. However, many problems may remain undiscovered. Abstract: Static analysis is an essential way to find code Static analysis is a widely-used method which is by smells and bugs. It checks the source code without exe- definition the act of uncovering properties and reasoning cution and no test cases are required, therefore its cost is about software without observing its runtime behaviour, lower than testing. Moreover, static analysis can help in restricting the scope of tools to those which operate on the software engineering comprehensively, since static anal- source representation, the code written in a single or mul- ysis can be used for the validation of code conventions, tiple programming languages. While most static analysis for measuring software complexity and for executing code methods are designed to detect anomalies (called bugs) in refactorings as well. Symbolic execution is a static analy- software code, the methods they employ are varied [1]. One sis method where the variables (e.g. input data) are inter- major difference is the level of abstraction at which the preted with symbolic values. code is represented [2]. Because static analysis is closely Clang Static Analyzer is a powerful symbolic execution related to the compilation of the code, the formats used engine based on the Clang compiler infrastructure that to represent the different abstractions are not unique to can be used with C, C++ and Objective-C.
    [Show full text]
  • SMT-Based Refutation of Spurious Bug Reports in the Clang Static Analyzer
    SMT-Based Refutation of Spurious Bug Reports in the Clang Static Analyzer Mikhail R. Gadelha∗, Enrico Steffinlongo∗, Lucas C. Cordeiroy, Bernd Fischerz, and Denis A. Nicole∗ ∗University of Southampton, UK. yUniversity of Manchester, UK. zStellenbosch University, South Africa. Abstract—We describe and evaluate a bug refutation extension bit in a is one, and (a & 1) ˆ 1 inverts the last bit in a. for the Clang Static Analyzer (CSA) that addresses the limi- The analyzer, however, produces the following (spurious) bug tations of the existing built-in constraint solver. In particular, report when analyzing the program: we complement CSA’s existing heuristics that remove spurious bug reports. We encode the path constraints produced by CSA as Satisfiability Modulo Theories (SMT) problems, use SMT main.c:4:12: warning: Dereference of null solvers to precisely check them for satisfiability, and remove pointer (loaded from variable ’z’) bug reports whose associated path constraints are unsatisfi- return *z; able. Our refutation extension refutes spurious bug reports in ˆ˜ 8 out of 12 widely used open-source applications; on aver- age, it refutes ca. 7% of all bug reports, and never refutes 1 warning generated. any true bug report. It incurs only negligible performance overheads, and on average adds 1.2% to the runtime of the The null pointer dereference reported here means that CSA full Clang/LLVM toolchain. A demonstration is available at claims to nevertheless have found a path where the dereference https://www.youtube.com/watch?v=ylW5iRYNsGA. of z is reachable. Such spurious bug reports are in practice common; in our I.
    [Show full text]
  • Compiling and Makefiles
    Compiling C Programs Makefiles Compiling and Makefiles 2501ICT/7421ICTNathan René Hexel School of Information and Communication Technology Griffith University Semester 1, 2012 René Hexel Compiling and Makefiles Compiling C Programs Makefiles Outline 1 Compiling C Programs 2 Makefiles Using the make Utility Makefiles for Objective-C Code Makefiles for C++ Code René Hexel Compiling and Makefiles Compiling C Programs Makefiles Compiling C Programs Integrated Development Environment (IDE) Eclipse, XCode, Visual C++, Project Center, . Compiles programs at the press of a button (like BlueJ) Often difficult to customise Very rarely support multiple platforms and languages Command Line Requires manual invocation Requires knowledge of command line parameters Can be tedious for large projects Cross-platform and -language compilers (e.g. clang) Makefiles Combine the best of both worlds Recompile a complex project with a simple make command René Hexel Compiling and Makefiles Compiling C Programs Makefiles Getting a Command Line Interface Via Dwarf ssh dwarf.ict.griffith.edu.au using putty (Windows) Via a local Terminal Mac OS X: e.g. Applications / Utilities / Terminal.app Linux: e.g. through the Gnome program menu Windows: e.g. Start / Programs / Programming Tools / GNUstep / Shell ) Enter commands to compile your program Hit Return (or Enter) after every command! René Hexel Compiling and Makefiles Compiling C Programs Makefiles Compiling a C program using clang or gcc Once on the command line change to the directory (folder) your program is in cd /my/example/directory
    [Show full text]
  • ENCM 335 Fall 2018: Command-Line C Programming on Macos
    page 1 of 4 ENCM 335 Fall 2018: Command-line C programming on macOS Steve Norman Department of Electrical & Computer Engineering University of Calgary September 2018 Introduction This document is intended to help students who would like to do ENCM 335 C pro- gramming on an Apple Mac laptop or desktop computer. A note about software versions The information in this document was prepared using the latest versions of macOS Sierra version 10.12.6 and Xcode 9.2, the latest version of Xcode available for that version of macOS. Things should work for you if you have other but fairly recent versions of macOS and Xcode. If you have versions that are several years old, though you may experience difficulties that I'm not able to help with. Essential Software There are several key applications needed to do command-line C programming on a Mac. Web browser I assume you all know how to use a web browser to find course documents, so I won't say anything more about web browsers here. Finder Finder is the tool built in to macOS for browsing folders and files. It really helps if you're fluent with its features. Terminal You'll need Terminal to enter commands and look at output of commands. To start it up, look in Utilities, which is a folder within the Applications folder. It probably makes sense to drag the icon for Terminal to the macOS Dock, so that you can launch it quickly. macOS Terminal runs the same bash shell that runs in Cygwin Terminal, so commands like cd, ls, mkdir, and so on, are all available on your Mac.
    [Show full text]
  • Compiling Linux with LLVM
    Open Source Open Possibilities Compiling Linux with LLVM Presented by: Mark Charlebois Presentation Date: 06/07/2012 PAGE 1 Open Source Open Possibilities Agenda Why would I want to use Clang to compile Linux? Status updates: cross compiling for ARM with Clang building Linux kernel with Clang running Linux compiled with Clang To do list PAGE 2 Open Source Open Possibilities Open Source Open Possibilities Why Would I Want to Use Clang to Compile Linux? PAGE 3 Open Source Open Possibilities Better Diagnostics $ gcc-4.2 -fsyntax-only t.c t.c:7: error: invalid operands to binary + (have 'int' and 'struct A') $ clang -fsyntax-only t.c t.c:7:39: error: invalid operands to binary expression ('int' and 'struct A') return y + func(y ? ((SomeA.X + 40) + SomeA) / 42 + SomeA.X : SomeA.X); ~~~~~~~~~~~~~~ ^ ~~~~~ See http://clang.llvm.org/diagnostics.html for more examples GCC extensions: all extensions are explicitly recognized as such and marked with extension diagnostics, which can be mapped to warnings, errors, or just ignored. Google builds their products also with Clang just for the better debug output Rich diagnostic output enables auto-generation of patches PAGE 4 Open Source Open Possibilities Fix-it Hints "Fix-it" hints provide advice for fixing small, localized problems in source code. $ clang t.c t.c:5:28: warning: use of GNU old-style field designator extension struct point origin = { x: 0.0, y: 0.0 }; ~~ ^ .x = t.c:5:36: warning: use of GNU old-style field designator extension struct point origin = { x: 0.0, y: 0.0 }; ~~ ^ .y = PAGE 5
    [Show full text]
  • Code Transformation and Analysis Using Clang and LLVM Static and Dynamic Analysis
    Code transformation and analysis using Clang and LLVM Static and Dynamic Analysis Hal Finkel1 and G´abor Horv´ath2 Computer Science Summer School 2017 1 Argonne National Laboratory 2 Ericsson and E¨otv¨osLor´adUniversity Table of contents 1. Introduction 2. Static Analysis with Clang 3. Instrumentation and More 1 Introduction Space of Techniques During this set of lectures we'll cover a space of techniques for the analysis and transformation of code using LLVM. Each of these techniques have overlapping areas of applicability: Static Analysis LLVM Instrumentation Source Transformation 2 Space of Techniques When to use source-to-source transformation: • When you need to use the instrumented code with multiple compilers. • When you intend for the instrumentation to become a permanent part of the code base. You'll end up being concerned with the textual formatting of the instrumentation if humans also need to maintain or enhance this same code. 3 Space of Techniques When to use Clang's static analysis: • When the analysis can be performed on an AST representation. • When you'd like to maintain a strong connection to the original source code. • When false negatives are acceptable (i.e. it is okay if you miss problems). https://clang-analyzer.llvm.org/ 4 Space of Techniques When to use IR instrumentation: • When the necessary conditions can be (or can only be) detected at runtime (often in conjunction with a specialized runtime library). • When you require stronger coverage guarantees than static analysis. • When you'd like to reduce the cost of the instrumentation by running optimizations before the instrumentation is inserted, after the instrumentation is inserted, or both.
    [Show full text]
  • LLVM Sanitizers
    LLVM and the state of sanitizers on BSD Speaker : David Carlier Software engineer living in Ireland, contribute to various opensource projects directly or indirectly related to FreeBSD and OpenBSD mainly, from enterprise solutions to more entertaining ones like video games, contributor LLVM since end of 2017, committer since May 2018. Write time to time for BSDMag. Status on FreeBSD and OpenBSD How it had started ? ● It often starts from “frustration” :-). ● Indeed, after having tried fuzzer under Linux, I realized it was not supported under FreeBSD. ● After this came Xray instrumentation and MemorySanitizer. ● Somewhere in between, started to port UndefinedBehaviorSanitizer, libFuzzer and Xray as well.. ● After getting into enough people's nerves, you get commit access. Where are we ? FreeBSD OpenBSD asan ubsan safestack libFuzzer msan Xray instrumentation libFuzzer Cannot have asan/msan/tsan Xray instrumentation ASLR cannot be disabled Cannot map large regions ubsan (shadow memory) What is fuzzing all about ? ● It is a testing technique, “invented” in late 80'a by Barton Miller, when basically you try to give random data to your software and its dependencies included. ● Inputs source come from what call “corpus” ● It is good to find particular set of bugs, based on input handling basically while trying to cover as much as possible code paths by mutating these inputs. ● Ideally running long, as the data will undergo some “mutation” in the process, as necessary until it crashes eventually. ● Completes traditional unit tests set too. What corpus means ? ● Place holder for inputs, inputs which suit the particular software. ● Let's imagine an image library reader which relies on specific binary format header to recognise if it is png/jpeg and so on.
    [Show full text]
  • Using Clang-Tidy and Clang-Format.Pdf
    Using clang-tidy and clang-format Linux Plumbers Conf 2020 - LLVM MC Miguel Ojeda, Nathan Huckleberry What is Clang Tooling? ● Clang is one of the LLVM compiler frontends ● But it is also designed as a platform for building source level tools ○ Syntax checking ○ Automatic fixing of compile errors ○ Code formatting ○ Refactoring ○ Linting ○ Static code analysis ○ … What could the kernel use Clang Tooling for? ● In the kernel we already use a lot of custom tools ○ sparse ○ spatch (Coccinelle) ○ checkpatch.pl ○ … ● Clang Tooling allows us to build more of them ○ Without having to deal with parsing C code ○ With support for all C extensions we use ○ With easy access to the AST (Abstract Syntax Tree) clang-format — What is it? ● A tool to format C-like code ○ Supports different languages ○ Many configurable rules and heuristics ○ Very fast ○ Good enough ● Allows us to spend less time on formatting and reviewing style ● Kernel style already pre-configured for you ○ Overriding the global style for particular subsystems is possible ○ See .clang-format clang-format — Example static inline void cpuhp_lock_acquire ( bool bringup ){ lock_map_acquire ( bringup ? & cpuhp_state_up_map : & cpuhp_state_down_map ); } clang-format — Example static inline void cpuhp_lock_acquire ( bool bringup ){ lock_map_acquire ( bringup ? & cpuhp_state_up_map : & cpuhp_state_down_map ); } static inline void cpuhp_lock_acquire(bool bringup) { lock_map_acquire(bringup ? &cpuhp_state_up_map : &cpuhp_state_down_map); } clang-format — Common use cases ● Re-formatting blocks ○ After indenting to keep line length within the limit ○ After refactoring and moving code around ● Re-formatting full files ● Sorting #includes ● Aligning ○ Variable blocks (on types or on the =) ○ Multi-line macro continuations (\) ● Reflowing comments ● ... clang-format — Kernel use cases ● Re-formatting patches ○ Clang provided script: clang-format-diff.py ○ Useful to spot coding style mistakes, typos, etc.
    [Show full text]
  • The Android Platform Security Model∗
    The Android Platform Security Model∗ RENÉ MAYRHOFER, Google and Johannes Kepler University Linz JEFFREY VANDER STOEP, Google CHAD BRUBAKER, Google NICK KRALEVICH, Google Android is the most widely deployed end-user focused operating system. With its growing set of use cases encompassing communication, navigation, media consumption, entertainment, finance, health, and access to sensors, actuators, cameras, or microphones, its underlying security model needs to address a host of practical threats in a wide variety of scenarios while being useful to non-security experts. The model needs to strike a difficult balance between security, privacy, and usability for end users, assurances for app developers, and system performance under tight hardware constraints. While many of the underlying design principles have implicitly informed the overall system architecture, access control mechanisms, and mitigation techniques, the Android security model has previously not been formally published. This paper aims to both document the abstract model and discuss its implications. Based on a definition of the threat model and Android ecosystem context in which it operates, we analyze how the different security measures in past and current Android implementations work together to mitigate these threats. There are some special cases in applying the security model, and we discuss such deliberate deviations from the abstract model. CCS Concepts: • Security and privacy → Software and application security; Domain-specific security and privacy architectures; Operating systems security; • Human-centered computing → Ubiquitous and mobile devices. Additional Key Words and Phrases: Android, security, operating system, informal model 1 INTRODUCTION Android is, at the time of this writing, the most widely deployed end-user operating system.
    [Show full text]
  • Compiling Android Userspace and Linux Kernel with LLVM
    Compiling Android userspace and Linux Kernel with LLVM Nick Desaulniers, Greg Hackmann, and Stephen Hines* October 18, 2017 *This was/is a really HUGE effort by many other people/teams/companies. We are just the messengers. :) Making large changes is an adventure ● Change via decree/mandate can work, … ● But we found it much easier to build up through sub-quests. ○ Initial Clang/LLVM work was not intending to replace GCC. ○ Eventually, a small group of people saw change as the only reasonable path forward. ○ Small, incremental improvements/changes are easier. ○ Got partners, vendors, and even teams from other parts of Google involved early. ○ Eventually, the end goal was clear: ■ “It’s time to have just one compiler for Android. One that can help find (and mitigate) security problems.” Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem Grow your support Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem A Brief History of LLVM and Android ● 2010 — RenderScript project begins ○ Used LLVM bitcode as portable IR (despite repeated warnings NOT to). :P ○ On-device bitcode JIT (later becomes AOT, but actual code generation is done on device). ○ Uses same LLVM on-device as for building host code with Clang/LLVM - we <3 bootstrapping! ● March 2012 — LOCAL_CLANG appears (Gitiles). ○ Compiler-rt (for ASan), libpng, and OpenSSL are among the first users. ○ Other users appear as extension-related ABI issues spring up. ● April 2014 — Clang for platform != LLVM on-device (AOSP / Gitiles). ● July 2014 — All host builds use Clang (AOSP / Gitiles). Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    [Show full text]
  • Opencl Overview and Update
    OpenCL Overview and Update Neil Trevett | Khronos President NVIDIA Vice President Developer Ecosystem OpenCL Working Group Chair [email protected] | @neilt3d Santa Clara, May 2019 © Copyright Khronos® Group 2019 - Page 1 Khronos Mission Khronos members are industry leaders from around the world that join to safely cooperate - to advance their own businesses and the industry as a whole Software Silicon Khronos is an open, member-driven industry consortium developing royalty-free standards, and vibrant ecosystems, to harness the power of silicon acceleration for demanding graphics rendering and computationally intensive applications © Copyright Khronos® Group 2019 - Page 2 Active Khronos Standards Industry involvement, engagement and feedback are the lifeblood of any successful standard © Copyright Khronos® Group 2019 - Page 3 Levels of Khronos Engagement Open to all! https://community.khronos.org/c/opencl www.khr.io/slack Spec fixes and suggestions made under the Khronos IP Framework. Open source contributions OpenCL Forum under repo’s CLA – typically Apache 2.0 and Slack Channel https://github.com/KhronosGroup Contribute to open source Advisors under the Khronos IP specs, CTS and tools Framework can comment and contribute to requirements and draft specifications Advisory Panel Khronos members under IP Framework and NDA can participate and vote in working group meetings Working Group © Copyright Khronos® Group 2019 - Page 4 OpenCL Heterogeneous Computing A programming and runtime framework for heterogeneous compute resources Low-level
    [Show full text]