DOCSLIB.ORG

Mclinker - the final Toolchain Frontier

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mclinker - the final Toolchain Frontier MCLinker - the final toolchain frontier J¨orgSonnenberger March 16, 2013 Abstract Google gold on the other hand mixes the first two phases. Symbols that can't be resolved in the first LLVM and Clang provide the top half of an inte- round are retried later. This choice improves the grated BSD licensed cross-platform toolchain. The maintainability of performance of the linker code, MCLinker project implements the remaining parts. but is still more complicated than the design of It is compact, modular and efficient. Currently MCLinker. It is useful to note that gold supports supported platforms are ELF systems running X86 multi-threading during the relocation processing to (32bit and 64bit), ARM and MIPS. MIPS64 and speed up linking large input sets. Hexagon are work-in-progress. 2.1 Input tree 1 Introduction The input tree is the first intermediate representa- Following the GPL3 announcement of the Free Soft- tion (IR) used by MCLinker. It contains vertices ware Foundation, the LLVM project gained a lot for every input file and all positional options. Posi- of traction. The Clang front-end allows replac- tional options are options like {start-group or {as- ing GCC for C and C++ code on many impor- needed that change the handling of a subset of the tant platforms. The Machine Code layer provides input files. Input files can form subtrees, e.g. linker an integrated assembler, replacing the dependency archives form a subtree with a child node for every on external assemblers for most situations. The archive member. Edges in the input graph are ei- combination provides a powerful toolchain with full ther positional relationships for options or inclusion support for cross-compilation. For a long time, links for archives. the only major component missing to replace GNU binutils has been a linker. This gap is now filled by 2.2 Symbol resolution the Machine Code Linker (MCLinker) project. This paper first introduces the architecture of Symbol resolution is implemented using tree itera- MCLinker and compares it to GNU ld. The perfor- tion. As result of symbol resolution, the low-level mance for linking large programs is evaluated and IR is created: the fragment reference graph. This compared with GNU ld and Google gold. A de- graph represents the individual sections found dur- tailed status report of the implementation is pre- ing input process and the symbolic dependencies sented as well as list of future projects. between them. The input tree is traversed and for every input file it is checked whether it must be included in the 2 Architecture output. An input file is included if it was explicitly mentioned on the command line or if it provides MCLinker is a modern, modular linker. It is de- a definition for a currently undefined symbol. If signed to process input in three separate phases: the input is to be included, its sections and symbol • Building the input tree based on command line table are processed. When the tree iteration hits and implicit default values. the start of a linker group, the current position is pushed onto a stack. Iteration continues until the • Resolve symbols. corresponding end is seen. The linker now checks if any new undefined reference was found while pro- • Determine output positions, apply relocations cessing this group. If so, the process starts again and write output files. from memorized position. GNU ld doesn't have a clear phase separation; The data structures used for symbol resolution individual steps are re-applied iteratively until all are highly optimized to maximize cache locality. input files are processed and all resolvable symbols The symbol attributes and the initial part of the are resolved. The result is complicated and cache- name share a cache line on modern CPUs. This unfriendly code. helps the CPU when linking large programs with many smaller functions; C++ applications are well- The resulting binaries have the following size: known for such characteristics. MCLinker GNU ld gold llvm-tblgen .text 2,123,527 1,827,773 1,786,483 2.3 Layout .data 2,408 2,664 2,520 .bss 5,360 5,912 2,520 The layout step is the first part of the last linking phase. It is responsible for deciding what sections clang should be written in which order and to what posi- .text 34,299,746 26,917,022 26,698,448 tion. It merges sections as necessary or drops them, .data 21,984 22,112 22,112 if they are redundant (e.g. multiple inline defini- .bss 47,624 47,736 47,704 tions for C++ methods). At the end of this phase, Both MCLinker and gold are significantly faster the symbol values are finalized. than GNU ld. MCLinker is clearly pulling in too many objects, which is responsible for the much Defering the section merging until such a late larger binaries. This is likely also reponsible for step in the linking process has the advantage of a good part of the performance difference to gold. avoiding many redundant computations. The list Evidently, further analysis is needed. of all input sections is known at this point and af- Of special interest for embedded use is ter a single ordering pass, addresses can be assigned the memory footprint of the different linkers: directly. MCLinker GNU ld gold llvm-tblgen 17,508KB 17,700KB 17,528KB 2.4 Relocation clang 176MB 150MB 182MB The peak Resident Memory Size shows clearly The relocation step follows the layout step and is re- that both MCLinker and gold are optimised for in- sponsible for determining the symbol values in the memory processing. Since they are reading the full various places that reference the symbols. It may symbol tables of all input files first, they require prepare to modify the instructions to replace more more memory. costly code with simpler sequences. This helps platforms with limited immediate value ranges like ARM and MIPS to load short (relative) address di- 4 Implementation status rectly instead of using constant tables. It can also be used to use more efficient access methods for Linker functionality falls into two categories. The Thread Local Storage (TLS). first is generic features like symbol versioning which are handled in the platform independent core. The second is features specific to a target platform like 2.5 Writing the handling of the different relocation types. Once the relocation step is done, all that is left is 4.1 Platform independent applying the relocations to the input sections and writing the result to the output file with any meta- Most features necessary for ELF systems are im- data necessary for the file format. MCLinker ag- plemented. This includes static and shared linkage gressively uses memory mapped files when possible. as well partially linking objects to form a new re- This leverages the page lookup table (TLB) cache locatable object. Weak symbols are overwritten by and improves page locality. It helps improves the strong definitions. The different visibility types are use of the OS file system cache. handled. Missing for shared libraries is the process- ing of DT NEEDED entries and loading the sym- bols of the referenced objects. This means that cur- 3 Performance rently only symbols in libraries explicitly requested on the command line are found, when standard To measure the performance of MCLinker, the ELF behavior is to recursively scan libraries and llvm-tblgen and clang binaries were built using the their dependencies. This omission is not absolved normal options in NetBSD (-O2, no -g). The fi- by recent versions of GNU ld switching to the same nal linker invocation was repeated using MCLinker, broken semantic. GNU ld and Google gold. For MCLinker the cur- C++ requires constructor and destructor sup- rent development version of March 11 was used. port. The compiler uses .ctors or .init array sec- GNU ld and gold are both from GNU binutils tions (or .dtor and .fini array for destructors) to 2.22.90. implement this. MCLinker has full support for ei- MCLinker GNU ld gold ther form. It doesn't try to convert one mecha- llvm-tblgen 0.05s 0.10s 0.04s nism into the other due to the slightly different clang 0.69s 1.41s 0.44s ordering rules. Support for COMDAT-sections is present. This allows defining the implemention of 5 Future work a function in more than one object file and let- ting the linker pick one. It is used for implicit The biggest priority for the MCLinker project is to template specialisations. The .eh frame sections finish the missing platform independent features. necessary for exception handling are correctly pro- This means adding symbol versioning and linker cessed and the associated .eh frame hdr section is script support. Another important item is support created. The latter provides a fast binary search for Link Time Optimisation (LTO). Open research table to reduce runtime overhead. One issue in this questions include the impact of fine-grained layout area is the missing support for relocations into the decisions by creating individual sections for every .eh frame section. This is needed for support the function in the compiler and letting the linker figure older register frame info style shared library in- out the best placement. terface. Support for the alternative 32bit ABI on X86 The platform-independent part of TLS support (X32), MIPS64 and Hexagon is work-in-progres. is present. This concerns the proper merging of the .tdata and .tbss sections and the corresponding segments. 6 Summary Support for symbol versioning is missing. For MCLinker provides a cross-compiling friendly linker NetBSD, it is only used by libgcc at the moment, so for many platforms targetted by the BSDs.
Load more

Recommended publications
  • Latent GOLD, Polca, and MCLUST
    JOBNAME: tast 63#1 2009 PAGE: 1 OUTPUT: Thursday January 15 07:45:17 2009 asa/tast/164303/SR3 Review of Three Latent Class Cluster Analysis Packages: Latent GOLD, poLCA, and MCLUST Dominique HAUGHTON, Pascal LEGRAND, and Sam WOOLFORD McCutcheon (2002). Because LCA is based upon a statistical model, maximum likelihood estimates can be used to classify This article reviews three software packages that can be used cases based upon what is referred to as their posterior proba- to perform latent class cluster analysis, namely, Latent GOLDÒ, bility of class membership. In addition, various diagnostics are MCLUST, and poLCA. Latent GOLDÒ is a product of Statistical available to assist in the determination of the optimal number Innovations whereas MCLUST and poLCA are packages of clusters. written in R and are available through the web site http:// LCA has been used in a broad range of contexts including www.r-project.org. We use a single dataset and apply each sociology, psychology, economics, and marketing. LCA is software package to develop a latent class cluster analysis for presented as a segmentation tool for marketing research and the data. This allows us to compare the features and the tactical brand decision in Finkbeiner and Waters (2008). Other resulting clusters from each software package. Each software applications in market segmentation are given in Cooil, package has its strengths and weaknesses and we compare the Keiningham, Askoy, and Hsu (2007), Malhotra, Person, and software from the perspectives of usability, cost, data charac- Bardi Kleiser (1999), Bodapati (2008), and Pancras and Sudhir teristics, and performance.
    [Show full text]
  • R Pass by Reference
    R Pass By Reference Unlidded Sherlock verjuices or imbibe some pancake ingenuously, however littery Winifield denitrifies detestably or jellified. Prasun rhubarbs simperingly while overnice Stanleigh witch thru or rent immemorially. Acescent and unprejudiced Tanney stints her distillations damming or jitterbugging luxuriously. Doing so any task in the argument and reference by value of the use it and data have no problems become hard to have been deactivated Thanks for sharing it. Modernization can operate much faster, simpler, and safer when supported with analysis tools and even code transformation tools. But by appending an element, they created a new hardware which, of course, did you update the reference. Joe, this is indeed excellent tutorial in your Java kitty. However, this section focuses on wade is afraid to template implementation. What are someone different types of Classes in Java? To insure goods are released, we need to begin able to decrement their reference counts once we no longer made them. You should contact the package authors for that. Limit the loop variable visibility to the except of cord loop. Protected member function can be simply fine. If she is a default constructor, compare those assignments to the initializations in the default constructor. Left clear Right sides of an assignment statement. What began the basic Structure of a Java Program? This can experience nasty bugs that are extremely hard to debug. Warn the two consecutive parameters share is same type. How can Convert Char To stuff In Java? Please lift the information below before signing in. NOTHING but pass by reference in Java.
    [Show full text]
  • Compiling C++ Files & Declarations and Definitions
    Compiling C++ files Compiling C++ files 143 Compiling C++ files Hello World 2.0 Hello World 2.0 In C++ the code is usually separated into header files (.h/.hpp) and implementation files (.cpp/.cc): sayhello.hpp #include <string> void sayhello(const std::string& name); sayhello.cpp #include "sayhello.hpp" #include <iostream> void sayhello(const std::string& name){ std::cout << "Hello " << name << '!' << std::endl; } Other code that wants to use this function only has to include sayhello.hpp. 144 Compiling C++ files Compiler Compiler Reminder: Internally, the compiler is divided into Preprocessor, Compiler, and Linker. Preprocessor: • Takes an input file of (almost) any programming language • Handles all preprocessor directives (i.e., all lines starting with #) and macros • Outputs the file without any preprocessor directives or macros Compiler: • Takes a preprocessed C++ (or C) file, called translation unit • Generates and optimizes the machine code • Outputs an object file Linker: • Takes multiple object files • Can also take references to other libraries • Finds the address of all symbols (e.g., functions, global variables) • Outputs an executable file or a shared library 145 Compiling C++ files Compiler Preprocessor Most common preprocessor directives: • #include: Copies (!) the contents of a file into the current file // include system file iostream: #include <iostream> // include regular file myfile.hpp: #include "myfile.hpp" • #define: Defines a macro #define FOO // defines the macro FOO with no content #define BAR 1 // defines the macro BAR as 1 • #ifdef/#ifndef/#else/#endif: Removes all code up to the next #else/#endif if a macro is set (#ifdef) or not set (#ifndef) #ifdef FOO ..
    [Show full text]
  • Khem Raj [email protected] Embedded Linux Conference 2014, San Jose, CA
    Khem Raj [email protected] Embedded Linux Conference 2014, San Jose, CA } Introduction } What is GCC } General Optimizations } GCC specific Optimizations } Embedded Processor specific Optimizations } What is GCC – Gnu Compiler Collection } Cross compiling } Toolchain } Cross compiling } Executes on build machine but generated code runs on different target machine } E.g. compiler runs on x86 but generates code for ARM } Building Cross compilers } Crosstool-NG } OpenEmbedded/Yocto Project } Buildroot } OpenWRT } More …. } On } controls compilation time } Compiler memory usage } Execution speed and size/space } O0 } No optimizations } O1 or O } General optimizations no speed/size trade-offs } O2 } More aggressive than O1 } Os } Optimization to reduce code size } O3 } May increase code size in favor of speed Property General Size Debug Speed/ Opt level info Fast O 1 No No No O1..O255 1..255 No No No Os 2 Yes No No Ofast 3 No No Yes Og 1 No Yes No } GCC inline assembly syntax asm ( assembly template : output operands : input operands : A list of clobbered registers ); } Used when special instruction that gcc backends do not generate can do a better job } E.g. bsrl instruction on x86 to compute MSB } C equivalent long i; for (i = (number >> 1), msb_pos = 0; i != 0; ++msb_pos) i >>= 1; } Attributes aiding optimizations } Constant Detection } int __builtin_constant_p( exp ) } Hints for Branch Prediction } __builtin_expect #define likely(x) __builtin_expect(!!(x), 1) #define unlikely(x) __builtin_expect(!!(x), 0) } Prefetching } __builtin_prefetch
    [Show full text]
  • Proceedings.Pdf
    Goals and scopes •The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. Participants are invited to submit research articles. We will not enforce any length restriction. However we expect papers of two kinds: –Short position papers describing emerging ideas. –Long research papers with deeper description of experiments and of research results. •We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: –Aspect-oriented programming, –Design patterns, –Experience reports, –Frameworks, –Implementation, –new dialects or languages implemented in Smalltalk, –Interaction with other languages, –Meta-programming and Meta-modeling, –Tools Publication •Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm •Authors of the best accepted papers will also be invited to submit extended versions for publication in a special issue of Elsevier "Science of Computer Programming: Methods of Software Design: Techniques and Applications" •Please submit your paper through EasyChair on http://www.easychair.org/conferences/?conf=iwst2012 Program Chairs •Loïc Lagadec Lab-STICC, UBO, France •Alain Plantec, Lab-STICC, UBO, France Program Committee •Gabriela Arevalo, Universidad Nacional de Quilmes, Agentina •Alexandre Bergel University of Chile •Andrew P. Black Portland State University, US •Marcus
    [Show full text]
  • In Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection For gcc version 6.1.0 (GCC) Richard M. Stallman and the GCC Developer Community Published by: GNU Press Website: http://www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 51 Franklin Street, Fifth Floor Tel 617-542-5942 Boston, MA 02110-1301 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988-2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being \Funding Free Software", the Front-Cover Texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ::::::::::::::::::::::::::::::::::::::::::::: 1 1 Programming Languages Supported by GCC ::::::::::::::: 3 2 Language Standards Supported by GCC :::::::::::::::::: 5 3 GCC Command Options ::::::::::::::::::::::::::::::: 9 4 C Implementation-Defined Behavior :::::::::::::::::::: 373 5 C++ Implementation-Defined Behavior ::::::::::::::::: 381 6 Extensions to
    [Show full text]
  • Libreoffice 3.4 Draw Guide
    LibreOffice 3.4 Draw Guide Drawing Vector Graphics in LibreOffice Copyright This document is Copyright © 2012 by its contributors as listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/), version 3.0 or later. All trademarks in this guide belong to their legitimate owners. Contributors Martin Fox John Cleland Jean Hollis Weber John A Smith Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgments This book is based on and updated from OpenOffice.org 3.3 Draw Guide. The contributors to that book are: Agnes Belzunce Daniel Carrera Martin Fox Thomas Hackert Regina Henschel Peter Hillier-Brook Jared Kobos Hazel Russman Gary Schnabl Bernd Schukat Wolfgang Uhlig Jean Hollis Weber Claire Wood Linda Worthington Publication date and software version Published 10 May 2012. Based on LbreOffice 3.4.6. Documentation for LibreOffice is available at http://www.libreoffice.org/get-help/documentation Contents Copyright..................................................................................................................................... 2 Note for Mac users...................................................................................................................... 5 Chapter 1 Introducing Draw..................................................................................................................7
    [Show full text]
  • Strategies for Unbridled Data Dissemination: an Emergency Operations Manual
    Strategies for Unbridled Data Dissemination: An Emergency Operations Manual Nikita Mazurov PhD Thesis Centre for Cultural Studies, Goldsmiths, University of London 1 Declaration To the extent that this may make sense to the reader, I declare that the work presented in this thesis is my own. Nikita Mazurov 2 Acknowledgements The notion that the work in a thesis is ‘one’s own’ doesn’t seem quite right. This work has benefited from countless insights, critiques, commentary, feedback and all potential other manner of what is after all, work, by those who were subjected to either parts or the entirety of it during encounters both formal and informal. To say nothing of the fact that every citation is an acknowledgement of prior contributory work in its own right. I may have, however, mangled some or all of the fine input that I have received, for which I bear sole responsibility. Certain images were copied from other publications for illustrative purposes. They have been referenced when such is the case. Certain other images were provided by sources who will rename anonymous for reasons of safety. Assistance with technical infrastructure in establishing a server for part of the project was provided by another anonymous source; anonymous for the same reason as above. 3 Abstract This project is a study of free data dissemination and impediments to it. Drawing upon post-structuralism, Actor Network Theory, Participatory Action Research, and theories of the political stakes of the posthuman by way of Stirnerian egoism and illegalism, the project uses a number of theoretical, technical and legal texts to develop a hacker methodology that emphasizes close analysis and disassembly of existent systems of content control.
    [Show full text]
  • Projet IRIS Le Financement Du Logiciel Libre
    Projet IRIS Le financement du logiciel libre Y-Lan Boureau Renaud Duplay St´ephane Lescuyer Julien Mairal Quentin Munier Annelise Rapha¨el Septembre 2005 Ecole´ Nationale Sup´erieure des T´el´ecommunications Cycle d'ouverture aux T´el´ecommunications 1 Table des mati`eres 1 Le monde du libre 3 1.1 Qu'est-ce que le logiciel libre ? . 4 1.1.1 La naissance du concept . 4 1.1.2 Les principes fondateurs . 5 1.2 Les besoins en financement . 8 1.2.1 Le cout^ humain . 8 1.2.2 Distribution des logiciels . 9 1.2.3 Communication efficace . 9 2 Les diff´erents modes de financement 12 2.1 Le financement par la communaut´e . 12 2.2 Services suppl´ementaires . 14 2.3 Entreprise : commande d'un logiciel . 15 2.4 SAV, maintenance, formation . 17 2.5 Produits d´eriv´es . 18 2.6 M´ec´enat priv´e . 18 2.7 Les Etats et le logiciel libre . 21 2.7.1 L'int´er^et des Etats pour le "libre" . 21 2.7.2 Une intervention mesur´ee des Etats . 22 2.7.3 Le soutien feutr´e des pays du Nord . 23 2.7.4 Le volontarisme des pays en voie de d´eveloppement . 26 2.7.5 Bilan . 29 3 Equilibre entre ces modes de financements : ´evolutions et perspectives 29 3.1 Les disparit´es du libre, deux exemples . 29 3.1.1 Ubuntu . 29 3.1.2 Debian . 32 3.2 Perspectives . 32 3.2.1 Ubuntu . 33 3.2.2 Debian .
    [Show full text]
  • What Makes LLD So Fast Slides with Presenter Notes
    What makes LLD so fast? Peter Smith, Linaro Contents and Introduction ● What we are covering Today ○ What job does a linker do? ○ How fast is LLD compared to GNU ld and gold? ○ LLD design and implementation choices. ○ Non technical factors. ● My history with Linkers ○ Working in the Linaro TCWG team on LLVM. ○ Have made contributions to LLD, focusing on Arm and AArch64. ○ Have previously worked on Arm’s embedded linker armlink. What job does a ● Components of an ELF file ● Generic linker design linker do? ● Finding content ● Layout ● Relocation What is a Linker? ● Levine defines in Linkers and Loaders ○ “Binds more abstract names to more concrete names, which permits programmers to write code using more abstract names” ○ In general concrete representations are higher performance but less flexible ● In practice a tool that glues together the outputs of separate compilation into a single output A linker is in many ways a slightly more sophisticated version of cat. The linker must copy the necessary data from all the input objects, rearrange it and resolve fixups. It is worth bearing this in mind when complaining that the linker is slow, just doing a cat of all the object files can also take a significant amount of time, particularly when debug information is involved. Important components of a relocatable object file Sections: Relocations: A calculation done at link time with Contiguous .text value written to contents of section ranges of main: in output. bytes with movabsq $.L.str, %rdi R_X86_64_64 .ro.data.str1.1 + 0 the same ... properties. callq printf R_X86_64_PLT32 printf - 4 ... Sections are the .rodata.str1.1 atoms of .asciz “Hello World” Symbols: linking.
    [Show full text]
  • Shell Scripting Expert Recipes for Linux, Bash, and More.Pdf
    SHELL SCRIPTING EXPERT RECIPES FOR LINUX, BASH, AND MORE INTRODUCTION . .xxix ⊲ PART I AbOUT THE INGREDIENTS CHAPTER 1 The History of Unix, GNU, and Linux . 3 CHAPTER 2 Getting Started . 15. CHAPTER 3 Variables . 33 CHAPTER 4 Wildcard Expansion . .67 CHAPTER 5 Conditional Execution . .83 CHAPTER 6 Flow Control Using Loops . 111 CHAPTER 7 Variables Continued . 139 CHAPTER 8 Functions and Libraries . 16. 1 CHAPTER 9 Arrays . 199 CHAPTER 10 Processes . 219 CHAPTER 11 Choosing and Using Shells . 255 ⊲ PART II RECIPES FOR UsING AND EXTENDING SYSTEM TOOLS CHAPTER 12 File Manipulation . 279 CHAPTER 13 Text Manipulation . 315 CHAPTER 14 Tools for Systems Administration . 353 ⊲ PART III RECIPES FOR SYSTEms ADMINISTRATION CHAPTER 15 Shell Features . 40. 9 CHAPTER 16 Systems Administration . 427 CHAPTER 17 Presentation . 459 CHAPTER 18 Data Storage and Retrieval . .471 CHAPTER 19 Numbers . 483 CHAPTER 20 Processes . 501 CHAPTER 21 Internationalization . .517 Continues ⊲ PART I V REFERENCE APPENDIX Further Reading . 529 GLOssARY . 533 INDEX . 539 Shell Scripting EXPERT ReCIPES FOR LINUX, BASH, AND MORE Shell Scripting EXPERT RECIPES FOR LINUX, BASH, AND MORE Steve Parker Shell Scripting: Expert Recipes for Linux, Bash, and More Published by John Wiley & Sons, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2011 by Steve Parker, Manchester, England Published by John Wiley & Sons, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-02448-5 ISBN: 978-1-118-16633-8 (ebk) ISBN: 978-1-118-16632-1
    [Show full text]
  • Open Source Compliance in the Enterprise
    OPEN SOURCE COMPLIANCE IN THE ENTERPRISE Sponsored by for the Open Compliance Summit 2018 IBRAHIM HADDAD, PHD WITH CONTRIBUTIONS FROM SHANE COUGHLAN AND KATE STEWART OPEN SOURCE COMPLIANCE IN THE ENTERPRISE 2nd Edition Ibrahim Haddad, PhD With contributions from Shane Coughlan and Kate Stewart Ibrahim Haddad, PhD Open Source Compliance in the Enterprise 2nd Edition Copyright © 2018 The Linux Foundation. All rights reserved. This book or any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of the publisher except for the use of brief quotations in a book review and certain other noncommercial uses permitted by copyright law. Printed in the United States of America First Edition, 2016 Second Edition, 2018 1 Letterman Drive Building D Suite D4700 San Francisco CA 94129 Open Source Compliance in the Enterprise Contents Chapter 1 16 INTRODUCTION TO OPEN SOURCE COMPLIANCE 16 A CHANGING BUSINESS ENVIRONMENT 16 ENTER OPEN SOURCE COMPLIANCE 19 Benefits of Ensuring Open Source Compliance 20 FAILURE TO COMPLY 20 Intellectual Property Failures 22 License Compliance Problems 24 Process Failures 26 LESSONS LEARNED 27 Ensure Compliance Prior to Product Shipment/Service Launch 27 Non-Compliance is Expensive 28 Relationships Matter 29 Training is Important 29 Chapter 2 30 ESTABLISHING AN OPEN SOURCE MANAGEMENT PROGRAM 30 OPEN SOURCE COMPLIANCE PROGRAM 30 Compliance Strategy 31 Inquiry Response Strategy 32 Policies and Processes 32 Compliance Teams 33 Tools 34 Web Presence 35 Education 36 Automation
    [Show full text]