Session 404 Doug Gregor Senior Engineer, LLVM Frontend Team
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Using the GNU Compiler Collection (GCC)
Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 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.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \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 ......................... -
The GNU Compiler Collection on Zseries
The GNU Compiler Collection on zSeries Dr. Ulrich Weigand Linux for zSeries Development, IBM Lab Böblingen [email protected] Agenda GNU Compiler Collection History and features Architecture overview GCC on zSeries History and current status zSeries specific features and challenges Using GCC GCC optimization settings GCC inline assembly Future of GCC GCC and Linux Apache Samba mount cvs binutils gdb gcc Linux ls grep Kernel glibc DB2 GNU - essentials UDB SAP R/3 Unix - tools Applications GCC History Timeline January 1984: Start of the GNU project May 1987: Release of GCC 1.0 February 1992: Release of GCC 2.0 August 1997: EGCS project announced November 1997: Release of EGCS 1.0 April 1999: EGCS / GCC merge July 1999: Release of GCC 2.95 June 2001: Release of GCC 3.0 May/August 2002: Release of GCC 3.1/3.2 March 2003: Release of GCC 3.3 (estimated) GCC Features Supported Languages part of GCC distribution: C, C++, Objective C Fortran 77 Java Ada distributed separately: Pascal Modula-3 under development: Fortran 95 Cobol GCC Features (cont.) Supported CPU targets i386, ia64, rs6000, s390 sparc, alpha, mips, arm, pa-risc, m68k, m88k many embedded targets Supported OS bindings Unix: Linux, *BSD, AIX, Solaris, HP/UX, Tru64, Irix, SCO DOS/Windows, Darwin (MacOS X) embedded targets and others Supported modes of operation native compiler cross-compiler 'Canadian cross' builds GCC Architecture: Overview C C++ Fortran Java ... front-end front-end front-end front-end tree Optimizer rtx i386 s390 rs6000 sparc ... back-end back-end back-end -
CS 403/503: Programming Languages
BNF for <expression> <expression> → identifier | number | CS 403 -<expression> | (<expression>) | <expression><operator><expression> Organization of Programming Languages <operator> → + | - | * | / Class 3 - August 30, 2001 Topics For Today Parse Tree Review of BNF (Chapter 2.1) Derivations and parse trees (Chapter 2.1) Binding time (Chapter 3.1) Object lifetime and storage slope * x + intercept management (Chapter 3.2) BNF Concept Review Another Parse Tree Terminal symbols: Actual items that are part of the language (0,1,+,-,*,/,etc.) Non-Terminal symbols: <expr>, <op>, etc. Rule/production: A single line of BNF Alternatives: Expressed with | Also: slope * x + intercept *: 0 or more occurrences +:1 or more occurrences 1 Binding Lifetimes • Binding lifetime: The period of time Def: A binding is an association, such between the creation and destruction of a as between an attribute and an entity, name-to-object binding • Object lifetime: The period of time or between an operation and a between the creation and destruction of symbol. an object • These don’t necessarily coincide Def: Binding time is the time at which a • EX. Reference parameters binding takes place. Possible binding times Object Lifetimes… 1. Language design time--e.g., bind operator …correspond to one of three principal symbols to operations 2. Language implementation time--e.g., bind fl. pt. storage allocation mechanisms: type to a representation Static objects: Object lifetime = program 3. Compile time--e.g., bind a variable to a type in C execution. Object bound to one storage or Java location from load time on. 4. Load time--e.g., bind a FORTRAN 77 variable to a memory cell (or a C static variable) Stack objects: Object lifetime = subroutine 5. -
Section “Common Predefined Macros” in the C Preprocessor
The C Preprocessor For gcc version 12.0.0 (pre-release) (GCC) Richard M. Stallman, Zachary Weinberg Copyright c 1987-2021 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. A copy of the license is included in the section entitled \GNU Free Documentation License". This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below). (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 Table of Contents 1 Overview :::::::::::::::::::::::::::::::::::::::: 1 1.1 Character sets:::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Initial processing ::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3 Tokenization ::::::::::::::::::::::::::::::::::::::::::::::::::: 4 1.4 The preprocessing language :::::::::::::::::::::::::::::::::::: 6 2 Header Files::::::::::::::::::::::::::::::::::::: 7 2.1 Include Syntax ::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.2 Include Operation :::::::::::::::::::::::::::::::::::::::::::::: 8 2.3 Search Path :::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.4 Once-Only Headers::::::::::::::::::::::::::::::::::::::::::::: 9 2.5 Alternatives to Wrapper #ifndef :::::::::::::::::::::::::::::: -
C++/CLI Language Specification
Ecma/TC39-TG5/2004/25 C++/CLI Language Specification Working Draft 1.5, Jun, 2004 Public Review Document Text highlighted like this indicates a placeholder for some future action. It might be a note from the editor to himself, or an indication of the actual or expected direction of some as-yet open issue. Note: In the spirit of the "Working Draft, Standard for Programming Language C++", this is an early draft. It’s known to be incomplet and incorrekt, and it has lots of bad formatting. Publication Time: 6/17/2004 11:44 PM Table of Contents Table of Contents Introduction....................................................................................................................................................xi 1. Scope............................................................................................................................................................. 1 2. Conformance ............................................................................................................................................... 2 3. Normative references .................................................................................................................................. 3 4. Definitions .................................................................................................................................................... 4 5. Notational conventions................................................................................................................................ 7 6. Acronyms and abbreviations -
Protecting the Stack with Metadata Policies and Tagged Hardware
2018 IEEE Symposium on Security and Privacy Protecting the Stack with Metadata Policies and Tagged Hardware Nick Roessler Andre´ DeHon University of Pennsylvania University of Pennsylvania [email protected] [email protected] Abstract—The program call stack is a major source of ex- stack data, or hijack the exposed function call mechanism in ploitable security vulnerabilities in low-level, unsafe languages a host of other malicious ways. like C. In conventional runtime implementations, the underlying Consequently, protecting the stack abstraction is critical stack data is exposed and unprotected, allowing programming errors to turn into security violations. In this work, we design for application security. Currently deployed defenses such as W X and stack canaries [2] make attacks more difficult to novel metadata-tag based, stack-protection security policies for ⊕ a general-purpose tagged architecture. Our policies specifically conduct, but do not protect against more sophisticated attack exploit the natural locality of dynamic program call graphs to techniques. Full memory safety can be retrofitted onto existing achieve cacheability of the metadata rules that they require. C/C++ code through added software checks, but at a high cost Our simple Return Address Protection policy has a performance overhead of 1.2% but just protects return addresses. The two of 100% or more in runtime overhead [3]. These expensive richer policies we present, Static Authorities and Depth Isola- solutions are unused in practice due to their unacceptably high tion, provide object-level protection for all stack objects. When overheads [4]. enforcing memory safety, our Static Authorities policy has a There is a long history of accelerating security policies with performance overhead of 5.7% and our Depth Isolation policy hardware to bring their overheads to more bearable levels has a performance overhead of 4.5%. -
Microsoft Visual Studio: an Integrated Windows Program Development Environment
Microsoft Visual Studio: An Integrated Windows Program Development Environment Microsoft Visual Studio • Self-contained environment for Windows program development: – Creating/editing – Compiling/linking (building) – Testing/debugging • IDE that accompanies Visual C++, Visual Basic, Visual C#, and other Microsoft Windows programming languages • See Chapter 2 & Appendix C of the Deitel text • Also Appendix C of the Gregory text Some Visual Studio Components • The Editors: C, C++, C#, VB source program text editors • cut/paste, color cues, indentation • generate source text files Resource Editors • Resources: Windows static data • Determine look and feel of an application – icons, bitmaps, cursors, menus, dialog boxes, etc. • graphical • generate resource script (.rc) files • integrated with text editor • created visually .NET Language Compilers • Unmanaged Code C/C++ Compiler – translates source programs to machine language – generates object (.obj) files for linker • Managed Code .NET Language Compilers – Many of them ? multi-language interoperability – Translate source programs to MSIL – Generate a “Portable Executable” that must be translated to target machine language by the CLR • Resource Compiler – Reads .rc file – Generates binary resource (.res) file for linker The Linker • Reads compiler .obj and .res files • Accesses C/C++/Windows libraries • Generates executable (.exe or .dll) Program Build and Run in the .NET Framework Common Language Runtime The Debugger • Powerful source code debugger • Integrated with all parts of Visual -
Migrating Large Codebases to C++ Modules
Migrating large codebases to C++ Modules Yuka Takahashi - The University of Tokyo Princeton University Oksana Shadura - UNL Vassil Vassilev Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !1 Agenda 1. Motivation of C++ Modules 2. C++ Modules in ROOT 3. C++ Modules in CMSSW 4. CMS Performance Results 5. Conclusion Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !2 Motivation of C++ Modules Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !3 Motivation of C++ Modules C++ Modules technology: - Cache parsed header file information - Avoid header re-parsing - Avoid runtime header parsing (In ROOT) - Part of C++20 Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !4 Motivation of C++ Modules #include <vector> Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !5 Motivation of C++ Modules #include <vector> Textual Include Precompiled Headers (PCH) Modules Expensive Inseparable Fragile Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !6 Motivation of C++ Modules …… TVirtualPad.h …… # 286 "/usr/include/c++/v1/vector" 2 3 #include "TVirtualPad.h" namespace std { inline namespace __1 { template <bool> class __vector_base_common vector #include <vector> Preprocess { __attribute__ #include <set> ((__visibility__("hidden"), __always_inline__)) __vector_base_common() Textual Include{} …… int main() { # 394 "/usr/include/c++/v1/set" 3 namespace std {inline namespace __1 { … set template <…> class set { original code public: typedef _Key key_type; …… .o Compile Parse int main { one big file! …… Yuka Takahashi 13.03.2019 Migrating large codebases to C++ Modules, ACAT 2019 !7 Motivation of C++ Modules Textual Include .c .o 1. -
C# Programming in Depth Lecture 4: Garbage Collection & Exception
Chair of Software Engineering C# Programming in Depth Prof. Dr. Bertrand Meyer March 2007 – May 2007 Lecture 4: Garbage Collection & Exception Handling Lisa (Ling) Liu Overview Scope and lifetime Garbage collection mechanism Exception handling C# programming lecture 4: Garbage Collection & Exception Handling 2 Scope and lifetime Scope of a variable is portion of program text within which it is declared ¾ Need not be contiguous ¾ In C#, is static: independent of data Lifetime or extent of storage is portion of program execution during which it exists ¾ Always contiguous ¾ Generally dynamic: dependent on data Class of lifetime ¾ Static: entire duration of program ¾ Local or automatic: duration of call or block execution (local variable) ¾ Dynamic: From time of allocation statement (new) to deallocation, if any. C# programming lecture 4: Garbage Collection & Exception Handling 3 Object lifetime in C# Memory allocation for an object should be made using the “new” keyword Objects are allocated onto the managed heap, where they are automatically deallocated by the runtime at “some time in the future” Garbage collection is automated in C# Rule: Allocate an object onto the managed heap using the new keyword and forget about it C# programming lecture 4: Garbage Collection & Exception Handling 4 Object creation When a call to new is made, it creates a CIL “newobj” instruction to the code module public static int Main (string[] args) { Car c = new Car(“Viper”, 200, 100); } IL_000c: newobj instance void CilNew.Car::.ctor (string, int32, -
24Th Embarcadero Developer Camp
RAD Studio XE3 The Developer Force Multiplier Mac OS X Windows 8 Mountain Lion C++11 64-bit Metropolis UI C99 Boost Visual LiveBindings C++ Bjarne Stroustrup C with Objects (1979) Modeled OO after Simula and Ada ○ But syntax and RTL based on C Classes Inheritance Inlining Default arguments Type checking CFront compiler A Brief History of C++ C++11 – A new Standard Language Library Rvalue references and move constructors Variadic templates constexpr - Generalized constant New string literals expressions User-defined literals Core language usability enhancements Multithreading memory model Initializer lists Uniform initialization Thread-local storage Type inference Explicitly defaulted and deleted Range-based for-loop special member functions Lambda functions and expressions Type long long int Alternative function syntax Static assertions Object construction improvement Allow sizeof to work on members Explicit overrides and final of classes without an explicit object Null pointer constant Control and query object alignment Strongly typed enumerations Allow garbage collected Right angle bracket implementations Explicit conversion operators Alias templates Threading facilities Unrestricted unions Tu p le types Hash tables Regular expressions General-purpose smart pointers Extensible random number facility Wrapper reference Polymorphic wrappers for function objects Type traits for metaprogramming 64-bit C++Builder for Windows C++11 support in BCC64 compiler VCL and FireMonkey Dinkumware STL for -
Generating Object Lifetime Traces with Merlin
Generating Object Lifetime Traces with Merlin MATTHEW HERTZ University of Massachusetts, Amherst STEPHEN M BLACKBURN Australian National University J ELIOT B MOSS University of Massachusetts, Amherst KATHRYN S McKINLEY University of Texas at Austin and DARKO STEFANOVIC´ University of New Mexico ÈÖÓÖÑÑÖ× Ö ÛÖØÒ ÖÔÐÝ ÖÓÛÒ ÒÙÑ Ö Ó ÔÖÓÖÑ× Ò Ó Ø ÐÒÙ׸ × ÂÚ Ò ¸ ØØ ÖÕÙÖ Ö Ö Ò ×ÑÙÐØÓÒ ×Ô ÜÔÐÓÖØÓÒ ÙÔ Ý ÒÐÒ Ô Ö ÙÒÖרÒÒ× Ó Ó ÐØÑ ÚÓÖ Ò Ò ×Ò Ó ÒÛ Ö ÐÓÖØÑ׺ ÏÒ ÒÖØÒ Ô Ø ÖÙØ¹ÓÖ ÑØÓ Ó Ó ÐØÑ× ÖÕÙÖ× ÛÓÐ¹Ô Ö Ø ÚÖÝ Ô ÓØÒØÐ Ô ÓÒØ Ò Ø ÔÖÓÖѺ Ø× ÔÖÓ × ÔÖÓØÚÐÝ ÜÔ Ò×Ú¸ Ö× ÓØÒ ÒÙÐØ Ý ÓÒÐÝ Ô ÖÓ ¸ ºº¸ ÚÖÝ ¿¾Ã ÝØ× Ó ÐÐÓ Ù× Ö Û Ï ÜØÒ Ø ×ØØ Ó Ø ÖØ ÓÖ ×ÑÙÐØÒ Ö ÐÓÖØÑ× Ò ØÛÓÛÝ׺ Öר¸ ÚÐÓÔ ÑØÓ ÓÐÓÝ ÓÖ ×ÑÙÐØÓÒ ×ØÙ× Ó ÝÒ Ö Ò ÔÖ×ÒØ Ö×ÙÐØ× ×ÓÛÒ Ø Ó ÖÒÙÐÖØÝ ÓÒ Ø× ×ÑÙÐØÓÒ׺ Ï ×ÓÛ ØØ ÖÒÙÐÖØÝ ÓØÒ ×ØÓÖØ× ×ÑÙÐØ Ö Ö×ÙÐØ× ÛØ Ô Û ÓÖ Ó ÔÖ×ÒØ Ò Ñ×ÙÖ Ø Ô Ó ÒÛ ÐÓÖØÑ ÅÖÐÒ ÐØÑ׺ ÅÖÐÒ ØÑרÑÔ× Ó Ò ÐØÖ Ù×× Ø ØÑרÑÔ× Ó Ó ØÓ ÛÒ ØÝ º Ì ÅÖÐÒ ÐÓÖØÑ × ÓÒ Ö Ô ÖÓÖÑ Ý Ø × ÖÑÒØÐ Ö×ÙÐØ× ×ÓÛ ØØ ÅÖÐÒ ÒÖØ ÓÚÖ ØÛÓ ÓÖÖ× Ó ÑÒØÙ ×Ý×ØÑº ÜÔ ×ØÖ ØÒ Ø ÑØÓ ØÖ ÚÖÝ Ó ÐÐÓ Ï Ð×Ó Ù× ÅÖÐÒ ØÓ ÔÖÓ Ú×ÙÐÞØÓÒ× Ó Ô ÚÓÖ ØØ ÜÔ Ó× ÒÛ Ó ÐØÑ ÚÓÖ׺ Categories and Subject Descriptors: D.3.4 [Programming Languages]: Processors—memory management (gar- bage collection) ÒÖÐ ÌÖÑ× ÐÓÖØÑ׸ ÄÒÙ׸ È ØÓÒÐ ÃÝ ÏÓÖ× Ò ÈÖ×× Ö ×Ò¸ Ó ÐØÑ ÒÐÝ×׸ ÒÖØÓÒ This work is supported by NSF grants CCR-0219587, ITR CCR-0085792, EIA-0218262, EIA-9726401, EIA- 030609, EIA-0238027, EIA-0324845, DARPA F33615-03-C-4106, Hewlett-Packard gift 88425.1, Microsoft Re- search, and IBM. -
Modern C++ Object-Oriented Programming
CPP Modern C++ Object-Oriented Programming ''Combine old and newer features to get the best out of the language'' Margit ANTAL 2020 C++ - Object-Oriented Programming Course content − Introduction to C++ − Object-oriented programming − Generic programming and the STL − Object-oriented design C++ - Object-Oriented Programming References − Bjarne Stroustrup, Herb Sutter, C++ Core Guidelines, 2017. rd − M. Gregoire, Professional C++, 3 edition, John Wiley & Sons, 2014. th − S. Lippman, J. Lajoie, B. E. Moo, C++ Primer, 5 edition, Addison Wesley, , 2013. th − S. Prata, C++ Primer Plus, 6 edition, Addison Wesley, 2012. − N. Josuttis, The C++ standard library. a tutorial and reference. Pearson Education. 2012. − A. Williams, C++ Concurrency in Action:Practical Multithreading. Greenwich, CT: Manning. 2012. Module 1 Introduction to C++ Introduction to C++ Content − History and evolution − Overview of the key features ● New built-in types ● Scope and namespaces ● Enumerations ● Dynamic memory: new and delete ● Smart pointers: unique_ptr, shared_ptr, weak_ptr ● Error handling with exceptions ● References ● The const modifier Introduction to C++ History and evolution − Creator: Bjarne Stroustrup 1983 − Standards: ● The first C++ standard − 1998 (C++98, major) − 2003 (C++03, minor) ● The second C++ standard − 2011 (C++11, major) – significant improvements in language and library − 2014 (C++14, minor) − 2017 (C++17, major) Introduction to C+ History and evolution − source: https://isocpp.org/std/status Introduction to C+ History and evolution − source: