DOCSLIB.ORG

Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset Installing and using LLVM 11.0.0 toolset Last Updated: 2021-06-03 Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset Installing and using LLVM 11.0.0 toolset Eva-Lotte Gebhardt [email protected] Zuzana Zoubkova [email protected] Olga Tikhomirova [email protected] Peter Macko Kevin Owen Vladimir Slavik Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract LLVM Toolset is a Red Hat offering for developers on the Red Hat Enterprise Linux platform. This Using LLVM Toolset guide provides an overview of this product, explains how to invoke and use different versions of LLVM tools, and links to resources with more in-depth information. Table of Contents Table of Contents .M . A. .K . I.N . .G . .O . P. .E . N. S. .O . U. .R . C. .E . .M . .O . R. .E . .I N. .C . L. .U . S. .I V. .E . .4 . .C . H. .A . P. .T .E . R. 1.. .L . L. .V . M. 5. 1.1. ABOUT LLVM TOOLSET 5 1.2. COMPATIBILITY 5 1.3. GETTING ACCESS TO LLVM TOOLSET ON RED HAT ENTERPRISE LINUX 7 6 Prerequisites 6 Procedure 6 Additional Resources 7 1.4. INSTALLING LLVM TOOLSET 7 1.4.1. Installing CMake on Red Hat Enterprise Linux 8 1.4.1.1. CMake installable documentation 8 1.4.2. Installable documentation 8 1.5. ADDITIONAL RESOURCES 8 Online documentation 8 .C . H. .A . P. .T .E . R. 2. U. .S . I.N . .G . .C . L. .A . N. .G . 9. 2.1. COMPILING A C SOURCE FILE TO A BINARY FILE 9 2.2. COMPILING A C SOURCE FILE TO AN OBJECT FILE 10 2.3. LINKING C OBJECT FILES TO A BINARY FILE 10 2.4. USING THE CLANG INTEGRATED ASSEMBLER 10 2.5. RUNNING A C PROGRAM 11 2.6. ADDITIONAL RESOURCES 11 Installed documentation 11 Online documentation 11 See Also 11 .C . H. .A . P. .T .E . R. 3. U. S. I.N . .G . .C . L. .A . N. .G . .+ .+ . 1. 2. 3.1. COMPILING A C++ SOURCE FILE TO A BINARY FILE 12 3.2. COMPILING A C++ SOURCE FILE TO AN OBJECT FILE 12 3.3. LINKING C++ OBJECT FILES TO A BINARY FILE 12 3.4. RUNNING A C++ PROGRAM 13 3.5. ADDITIONAL RESOURCES 14 Installed documentation 14 Online documentation 14 See Also 14 .C . H. .A . P. .T .E . R. 4. .L .L . D. .B . 1. 5. 4.1. PREPARING A PROGRAM FOR DEBUGGING 15 4.2. RUNNING LLDB 15 4.3. LISTING THE SOURCE CODE 16 4.4. USING BREAKPOINTS 17 Setting a New Breakpoint 17 Listing Breakpoints 17 Deleting Existing Breakpoints 18 4.5. STARTING EXECUTION 18 4.6. DISPLAYING CURRENT PROGRAM DATA 19 4.7. CONTINUING EXECUTION AFTER A BREAKPOINT 19 4.8. ADDITIONAL RESOURCES 21 Online documentation 21 See also 21 1 Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset .C . H. .A . P. .T .E . R. 5. C. .O . .N . T. .A . I.N . E. .R . .I M. A. .G . E. .S . .W . .I T. .H . .L .L . V. .M . T. O. O. .L . S. .E .T . 2. 2. 5.1. USING UBI REPOSITORIES 22 5.2. EXAMPLE: BUILDING A CONTAINER IMAGE OF LLVM ON RHEL 8 USING A DOCKERFILE 22 5.3. EXAMPLE: BUILDING A CONTAINER IMAGE OF LLVM ON RHEL 7 USING A DOCKERFILE 22 5.4. ADDITIONAL RESOURCES 23 .C . H. .A . P. .T .E . R. 6. .C . H. .A . N. .G . .E .S . .I N. L. .L . V. .M . .1 .1 ..0 . ..0 . .T . O. .O . .L .S . E. .T . .2 . 4. 2 Table of Contents 3 Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset MAKING OPEN SOURCE MORE INCLUSIVE Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message . 4 CHAPTER 1. LLVM CHAPTER 1. LLVM 1.1. ABOUT LLVM TOOLSET LLVM Toolset is a Red Hat offering for developers on the Red Hat Enterprise Linux platform. It provides the LLVM compiler infrastructure framework, the Clang compiler for the C and C++ languages, the LLDB debugger, and related tools for code analysis. LLVM Toolset is distributed as a part of Red Hat Developer Tools for Red Hat Enterprise Linux 7. LLVM Toolset is available as a module for Red Hat Enterprise Linux 8. The following components are available as a part of LLVM Toolset: Table 1.1. LLVM Components Name Version Description clang RHEL 7 — 11.0.1 An LLVM compiler front end for C RHEL 8 — 11.0.0 and C++. lldb RHEL 7 — 11.0.1 A C and C++ debugger using RHEL 8 — 11.0.0 portions of LLVM. compiler-rt RHEL 7 — 11.0.1 Runtime libraries for LLVM. RHEL 8 — 11.0.0 llvm RHEL 7 — 11.0.1 A collection of modular and RHEL 8 — 11.0.0 reusable compiler and toolchain technologies. libomp RHEL 7 — 11.0.1 A library for utilization of Open RHEL 8 — 11.0.0 MP API specification for parallel programming. lld RHEL 7 — 11.0.1 An LLVM linker. RHEL 8 — 11.0.0 python-lit RHEL 7 — 0.11.1 A software testing tool for LLVM- RHEL 8 — 0.11.0 and Clang-based test suites. IMPORTANT LLVM Toolset for Red Hat Enterprise Linux 7 also provides CMake as a separate package. On Red Hat Enterprise Linux 8, CMake is available in the system repository. For more information on how to install CMake, see Section 1.4, “Installing LLVM Toolset”. 1.2. COMPATIBILITY LLVM Toolset is available for Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 8 on the following architectures: 5 Red Hat Developer Tools 1 Using LLVM 11.0.0 Toolset AMD and Intel 64-bit architectures The 64-bit ARM architecture (Only RHEL 8) IBM Power Systems, Little Endian IBM Power Systems, Big Endian (Only RHEL 7) 64-bit IBM Z 1.3. GETTING ACCESS TO LLVM TOOLSET ON RED HAT ENTERPRISE LINUX 7 This chapter lists the steps to perform before installing LLVM Toolset on a Red Hat Enterprise Linux 7 system. Complete the following steps to attach a subscription that provides access to the repository for Red Hat Developer Tools, and then enable the Red Hat Developer Tools and Red Hat Software Collections repositories. Prerequisites Verify that wget is installed on your system. The tool is available from the default Red Hat Enterprise Linux repositories. To install it, run the following command as root: # yum install wget Procedure 1. Get the latest subscription data from the server: # subscription-manager refresh 2. Use the following command to register the system: # subscription-manager register You can also register the system by following the appropriate steps in Registering and Unregistering a System in the Red Hat Subscription Management document. 3. Display a list of all subscriptions that are available for your system and identify the pool ID for the subscription: # subscription-manager list --available This command displays the subscription name, unique identifier, expiration date, and other details related to it. The pool ID is listed on a line beginning with Pool ID. 4. Attach the subscription that provides access to the Red Hat Developer Tools repository. Use the pool ID you identified in the previous step. # subscription-manager attach --pool=<appropriate pool ID from the subscription> 5. Verify the list of subscriptions attached to your system: # sudo subscription-manager list --consumed 6 CHAPTER 1. LLVM 6. Enable the rhel-7-variant-devtools-rpms repository: # subscription-manager repos --enable rhel-7-variant-devtools-rpms Replace variant with the Red Hat Enterprise Linux system variant ( server or workstation).
Load more

Recommended publications
  • The LLVM Instruction Set and Compilation Strategy
    The LLVM Instruction Set and Compilation Strategy Chris Lattner Vikram Adve University of Illinois at Urbana-Champaign lattner,vadve ¡ @cs.uiuc.edu Abstract This document introduces the LLVM compiler infrastructure and instruction set, a simple approach that enables sophisticated code transformations at link time, runtime, and in the field. It is a pragmatic approach to compilation, interfering with programmers and tools as little as possible, while still retaining extensive high-level information from source-level compilers for later stages of an application’s lifetime. We describe the LLVM instruction set, the design of the LLVM system, and some of its key components. 1 Introduction Modern programming languages and software practices aim to support more reliable, flexible, and powerful software applications, increase programmer productivity, and provide higher level semantic information to the compiler. Un- fortunately, traditional approaches to compilation either fail to extract sufficient performance from the program (by not using interprocedural analysis or profile information) or interfere with the build process substantially (by requiring build scripts to be modified for either profiling or interprocedural optimization). Furthermore, they do not support optimization either at runtime or after an application has been installed at an end-user’s site, when the most relevant information about actual usage patterns would be available. The LLVM Compilation Strategy is designed to enable effective multi-stage optimization (at compile-time, link-time, runtime, and offline) and more effective profile-driven optimization, and to do so without changes to the traditional build process or programmer intervention. LLVM (Low Level Virtual Machine) is a compilation strategy that uses a low-level virtual instruction set with rich type information as a common code representation for all phases of compilation.
    [Show full text]
  • 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]
  • CUDA Flux: a Lightweight Instruction Profiler for CUDA Applications
    CUDA Flux: A Lightweight Instruction Profiler for CUDA Applications Lorenz Braun Holger Froning¨ Institute of Computer Engineering Institute of Computer Engineering Heidelberg University Heidelberg University Heidelberg, Germany Heidelberg, Germany [email protected] [email protected] Abstract—GPUs are powerful, massively parallel processors, hardware, it lacks verbosity when it comes to analyzing the which require a vast amount of thread parallelism to keep their different types of instructions executed. This problem is aggra- thousands of execution units busy, and to tolerate latency when vated by the recently frequent introduction of new instructions, accessing its high-throughput memory system. Understanding the behavior of massively threaded GPU programs can be for instance floating point operations with reduced precision difficult, even though recent GPUs provide an abundance of or special function operations including Tensor Cores for ma- hardware performance counters, which collect statistics about chine learning. Similarly, information on the use of vectorized certain events. Profiling tools that assist the user in such analysis operations is often lost. Characterizing workloads on PTX for their GPUs, like NVIDIA’s nvprof and cupti, are state-of- level is desirable as PTX allows us to determine the exact types the-art. However, instrumentation based on reading hardware performance counters can be slow, in particular when the number of the instructions a kernel executes. On the contrary, nvprof of metrics is large. Furthermore, the results can be inaccurate as metrics are based on a lower-level representation called SASS. instructions are grouped to match the available set of hardware Still, even if there was an exact mapping, some information on counters.
    [Show full text]
  • Implementing Continuation Based Language in LLVM and Clang
    Implementing Continuation based language in LLVM and Clang Kaito TOKUMORI Shinji KONO University of the Ryukyus University of the Ryukyus Email: [email protected] Email: [email protected] Abstract—The programming paradigm which use data seg- 1 __code f(Allocate allocate){ 2 allocate.size = 0; ments and code segments are proposed. This paradigm uses 3 goto g(allocate); Continuation based C (CbC), which a slight modified C language. 4 } 5 Code segments are units of calculation and Data segments are 6 // data segment definition sets of typed data. We use these segments as units of computation 7 // (generated automatically) 8 union Data { and meta computation. In this paper we show the implementation 9 struct Allocate { of CbC on LLVM and Clang 3.7. 10 long size; 11 } allocate; 12 }; I. A PRACTICAL CONTINUATION BASED LANGUAGE TABLE I The proposed units of programming are named code seg- CBCEXAMPLE ments and data segments. Code segments are units of calcu- lation which have no state. Data segments are sets of typed data. Code segments are connected to data segments by a meta data segment called a context. After the execution of a code have input data segments and output data segments. Data segment and its context, the next code segment (continuation) segments have two kind of dependency with code segments. is executed. First, Code segments access the contents of data segments Continuation based C (CbC) [1], hereafter referred to as using field names. So data segments should have the named CbC, is a slight modified C which supports code segments.
    [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]
  • Sham: a DSL for Fast Dsls
    Sham: A DSL for Fast DSLs Rajan Waliaa, Chung-chieh Shana, and Sam Tobin-Hochstadta a Indiana University, Bloomington, United States Abstract Domain-specific languages (DSLs) are touted as both easy to embed in programs and easy to optimize. Yet these goals are often in tension. Embedded or internal DSLs fit naturally with a host language, while inheriting the host’s performance characteristics. External DSLs can use external optimizers and languages but sit apart from the host. We present Sham, a toolkit designed to enable internal DSLs with high performance. Sham provides a domain-specific language (embedded in Racket) for implementing other high-performance DSLs, with transparent compilation to assembly code at runtime. Sham is well suited as both a compilation target for other embedded DSLs and for transparently replacing DSL support code with faster versions. Sham provides seamless inter-operation with its host language without requiring any additional effort from its users. Sham also provides a framework for defining language syntax which implements Sham’s own language interface as well. We validate Sham’s design on a series of case studies, ranging from Krishnamurthi’s classic automata DSL to a sound synthesis DSL and a probabilistic programming language. All of these are existing DSLs where we replaced the backend using Sham, resulting in major performance gains. We present an example-driven description of how Sham can smoothly enhance an existing DSL into a high-performance one. When compared to existing approaches for implementing high-performance DSLs, Sham’s design aims for both simplicity and programmer control. This makes it easier to port our techniques to other languages and frameworks, or borrow Sham’s innovations “à la carte” without adopting the whole approach.
    [Show full text]
  • Introduction to LLVM (Low Level Virtual Machine)
    Introduction to LLVM (Low Level Virtual Machine) Fons Rademakers CERN What is the LLVM Project? • Collection of compiler technology components ■ Not a traditional “Virtual Machine” ■ Language independent optimizer and code generator ■ LLVM-GCC front-end ■ Clang front-end ■ Just-In-Time compiler • Open source project with many contributors ■ Industry, research groups, individuals ■ See http://llvm.org/Users.html • Everything is Open Source, and BSD Licensed! (except GCC) • For more see: http://llvm.org/ 2 LLVM as an Open-Source Project • Abridged project history ■ Dec. 2000: Started as a research project at University of Illinois ■ Oct. 2003: Open Source LLVM 1.0 release ■ June 2005: Apple hires project lead Chris Lattner ■ June 2008: LLVM GCC 4.2 ships in Apple Xcode 3.1 ■ Feb. 2009: LLVM 2.5 3 Why New Compilers? • Existing Open Source C Compilers have Stagnated! • How? ■ Based on decades old code generation technology ■ No modern techniques like cross-file optimization and JIT codegen ■ Aging code bases: difficult to learn, hard to change substantially ■ Can’t be reused in other applications ■ Keep getting slower with every release 4 LLVM Vision and Approach • Build a set of modular compiler components: ■ Reduces the time & cost to construct a particular compiler ■ Components are shared across different compilers ■ Allows choice of the right component for the job ■ Focus on compile and execution times ■ All components written in C++, ported to many platforms 5 First Product - LLVM-GCC 4.2 • C, C++, Objective C, Objective C++, Ada and Fortran • Same GCC command line options • Supports almost all GCC language features and extensions • Supports many targets, including X86, X86-64, PowerPC, etc.
    [Show full text]
  • Polymorphisation: Improving Rust Compilation Times Through
    Polymorphisation: Improving Rust compilation times through intelligent monomorphisation David Wood (2198230W) April 15, 2020 MSci Software Engineering with Work Placement (40 Credits) ABSTRACT In addition, Rust's compilation model is different from Rust is a new systems programming language, designed to other programming languages. In C++, the compilation unit is a single file, whereas Rust's compilation unit is a provide memory safety while maintaining high performance. 1 One of the major priorities for the Rust compiler team is crate . While compilation times of entire C++ and entire to improve compilation times, which is regularly requested Rust projects are generally comparable, modification of a by users of the language. Rust's high compilation times are single C++ file requires far less recompilation than modifi- a result of many expensive compile-time analyses, a com- cation of a single Rust file. In recent years, implementation pilation model with large compilation units (thus requiring of incremental compilation into rustc has improved recom- incremental compilation techniques), use of LLVM to gen- pilation times after small modifications to code. erate machine code, and the language's monomorphisation Rust generates machine code using LLVM, a collection of strategy. This paper presents a code size optimisation, im- modular and reusable compiler and toolchain technologies. plemented in rustc, to reduce compilation times by intelli- At LLVM's core is a language-independent optimiser, and gently reducing monomorphisation through \polymorphisa- code-generation support for multiple processors. Languages tion" - identifying where functions could remain polymor- including Rust, Swift, Julia and C/C++ have compilers us- phic and producing fewer monomorphisations.
    [Show full text]
  • Formalizing the LLVM Intermediate Representation for Verified Program Transformations
    University of Pennsylvania ScholarlyCommons Departmental Papers (CIS) Department of Computer & Information Science 2012 Formalizing the LLVM Intermediate Representation for Verified Program Transformations Jianzhou Zhao University of Pennsylvania Santosh Nagarakatte University of Pennsylvania, [email protected] Milo Martin University of Pennsylvania, [email protected] Stephan A. Zdancewic University of Pennsylvania, [email protected] Follow this and additional works at: https://repository.upenn.edu/cis_papers Part of the Computer Sciences Commons Recommended Citation Jianzhou Zhao, Santosh Nagarakatte, Milo Martin, and Stephan A. Zdancewic, "Formalizing the LLVM Intermediate Representation for Verified Program Transformations", . January 2012. Jianzhou Zhao, Santosh Nagarakatte, Milo M. K. Martin, and Steve Zdancewic. Formalizing the LLVM Intermediate Representation for Verified Program Transformations. In Proc. of the ACM Symposium on Principles of Programming Languages (POPL), 2012 doi>10.1145/2103656.2103709 © ACM, 2012. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in Proc. of the ACM Symposium on Principles of Programming Languages, { (2012)} http://doi.acm.org/doi>10.1145/2103656.2103709" Email [email protected] This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_papers/560 For more information, please contact [email protected]. Formalizing the LLVM Intermediate Representation for Verified Program Transformations Abstract This paper presents Vellvm (verified LLVM), a framework for reasoning about programs expressed in LLVM's intermediate representation and transformations that operate on it. Vellvm provides a mechanized formal semantics of LLVM's intermediate representation, its type system, and properties of its SSA form.
    [Show full text]
  • “Which Targets Does Clang Support?”
    “Which targets does Clang support?” EuroLLVM 2014: Lightening Talk Jonathan Roelofs [email protected] mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. “Which targets does Clang support?” “Some stuff doesn’t seem to be documented at ALL…. what are the valid inputs to the ‘- arch’ … option? … This really is frustrating.” – Tim Hill [1] 2 “Which targets does Clang support?” “I read the man page … but I haven't been able to find a list of what ‘-march’ options are available…. Could someone point me to a list of supported options?” – Tim Nackos [2] 3 “Which targets does Clang support?” “I think the best way to get the answer is reading the source” – a’Q [3] 4 “Which targets does Clang support?” Clearly we need a better answer! 5 Prior Work 6 Prior Work $> clang –target <foo> --print-multi-libs (Based on patches I submitted earlier this spring) 7 Universal Driver “Clang is inherently a cross compiler…. However, actually cross compiling in practice involves much more than just generating the right assembly” – Daniel Dunbar [4] 8 Proposed Solution Target Triple: <arch><sub>-<vendor>-<sys>-<abi> --print-supported-archs --print-supported-vendors --print-supported-systems --print-supported-abis --print-multi-libs --print-available-targets 9 Proposed Solution: Examples $> clang --print-supported-archs x86 ... $> clang -march x86 --print-supported-systems auroraux darwin macosx ... $> clang -march x86 --print-available-systems linux 10 Proposed Solution: Examples $> clang --print-supported-targets x86-linux-gnu ppc-apple-darwin arm-none-eabi $> clang --print-available-targets x86-linux-gnu $> clang –target ppc-apple-darwin foo.c Sorry, but the toolchain for: ppc-apple-darwin has not been installed.
    [Show full text]
  • Bringing Next Generation C++ to Gpus
    Bringing Next Generation C++ to GPUs Michael Haidl1, Michel Steuwer2, Lars Klein1 and Sergei Gorlatch1 1University of Muenster, Germany 2University of Edinburgh, UK The Problem: Dot Product std::vector<int> a(N), b(N), tmp(N); std::transform(a.begin(), a.end(), b.begin(), tmp.begin(), std::multiplies<int>()); auto result = std::accumulate(tmp.begin(), tmp.end(), 0, std::plus<int>()); • The STL is the C++ programmers swiss knife • STL containers, iterators and algorithms introduce a high-level of abstraction • Since C++17 it is also parallel 1 The Problem: Dot Product std::vector<int> a(N), b(N), tmp(N); std::transform(a.begin(), a.end(), b.begin(), tmp.begin(), std::multiplies<int>()); auto result = std::accumulate(tmp.begin(), tmp.end(), 0, std::plus<int>()); f1.hpp f2.hpp template<typename T> template<typename T> auto mult(const std::vector<T>& a auto sum(const std::vector<T>& a){ const std::vector<T>& b){ return std::accumulate(a.begin(), std::vector<T> tmp(a.size()); a.end(), T(), std::plus<T>()); std::transform(a.begin(), a.end(), } b.begin(), tmp.begin(), std::multiplies<T>()); return tmp; } 1 The Problem: Dot Product std::vector<int> a(N), b(N); auto result = sum(mult(a, b)); f1.hpp f2.hpp template<typename T> template<typename T> auto mult(const std::vector<T>& a auto sum(const std::vector<T>& a){ const std::vector<T>& b){ return std::accumulate(a.begin(), std::vector<T> tmp(a.size()); a.end(), T(), std::plus<T>()); std::transform(a.begin(), a.end(), } b.begin(), tmp.begin(), std::multiplies<T>()); return tmp; } 1 f1.hpp f2.hpp
    [Show full text]
  • Llvmlinux: the Linux Kernel with Dragon Wings
    LLVMLinux: The Linux Kernel with Dragon Wings Presented by: Behan Webster (LLVMLinux project lead) Presentation Date: 2013.10.24 LLVMLinux Project What is Clang/LLVM? LLVMLinux Project LLVM is a Toolchain Toolkit A modular set of libraries for building tools Compiler, linker Source code analysis tools Meta data extraction from code Code refactoring tools Tight integration with IDEs LLVMLinux Project LLVM Toolchain Suite Clang (C/C++/Objective-C compiler) Compiler-rt (highly tuned low level operations) LLD and MC Linker (Linkers) Static Analyzer (checkers) LLDB (debugger) And more... LLVMLinux Project Why Would I Want to Use Clang/LLVM to Compile the Linux Kernel? LLVMLinux Project Fast Compiles Clang compiles code faster and use less memory than other toolchains Timed ImageMagick Compilation v6.8.1-10 Time To Compile Seconds, Less Is Better OpenBenchmarking.org GCC 4.7.2 58.05 SE +/- 0.07 GCC 4.8.0 59.67 SE +/- 0.12 LLVM Clang 3.2 25.03 SE +/- 0.11 LLVM Clang 3.3 SVN 24.79 SE +/- 0.10 13 26 39 52 65 Powered By Phoronix Test Suite 4.4.1 http://www.phoronix.com/scan.php?page=article&item=llvm_33svn_competes&num=1 LLVMLinux Project Fast Moving Project In just a few years Clang has reached and in some cases surpassed what other toolchains can do LAMMPS Molecular Dynamics Simulator v1.0 Test: Rhodopsin Protein Loop Time, Less Is Better OpenBenchmarking.org GCC 4.7.2 49.36 SE +/- 0.18 GCC 4.8.0 48.46 SE +/- 0.14 LLVM Clang 3.2 49.71 SE +/- 0.07 LLVM Clang 3.3 SVN 41.36 SE +/- 0.09 11 22 33 44 55 Powered By Phoronix Test Suite 4.4.1 1.
    [Show full text]