DOCSLIB.ORG

Red Hat Developer Toolset 1.X User Guide 1 Red Hat Developer Toolset 1.1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Red Hat Developer Toolset 1.x User Guide 1 Red Hat Developer Toolset 1.1 User Guide Installing and Using Red Hat Developer Toolset Edition 1 Jaromír Hradílek Red Hat Engineering Content Services [email protected] Jacquelynn East Red Hat Engineering Content Services [email protected] Matt Newsome Red Hat Software Engineering [email protected] 2 Legal Notice Legal Notice Copyright © 2012, 2013 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, JBoss, MetaMatrix, 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. All other trademarks are the property of their respective owners. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 Red Hat Developer Toolset 1.x User Guide 3 Abstract Red Hat Developer Toolset is a Red Hat offering for developers on the Red Hat Enterprise Linux platform. The Red Hat Developer Toolset User Guide provides an overview of this product, explains how to invoke and use the Developer Toolset versions of the tools, and links to resources with more in-depth information. 4 Table of Contents Table of Contents Preface 1. Document Conventions 1.1. Typographic Conventions 1.2. Pull-quote Conventions 1.3. Notes and Warnings 2. Getting Help and Giving Feedback 2.1. Do You Need Help? 2.2. We Need Feedback! I. Introduction 1. Red Hat Developer Toolset 1.1. About Red Hat Developer Toolset 1.2. Main Features 1.3. Compatibility 1.4. Getting Access to Red Hat Developer Toolset 1.4.1. Using RHN Classic 1.4.2. Using Red Hat Subscription Management 1.5. Installing Red Hat Developer Toolset 1.6. Updating Red Hat Developer Toolset 1.7. Uninstalling Red Hat Developer Toolset 1.8. Additional Resources II. Development Tools 2. GNU Compiler Collection (GCC) 2.1. GNU C Compiler 2.1.1. Installing the C Compiler 2.1.2. Using the C Compiler 2.1.3. Running a C Program 2.2. GNU C++ Compiler 2.2.1. Installing the C++ Compiler 2.2.2. Using the C++ Compiler 2.2.3. Running a C++ Program 2.3. GNU Fortran Compiler 2.3.1. Installing the Fortran Compiler 2.3.2. Using the Fortran Compiler 2.3.3. Running a Fortran Program 2.4. Additional Resources 3. GNU Debugger (GDB) 3.1. Installing the GNU Debugger 3.2. Preparing a Program for Debugging 3.3. Running the GNU Debugger 3.4. Listing Source Code 3.5. Setting Breakpoints 3.6. Starting Execution 3.7. Displaying Current Values 3.8. Continuing Execution 3.9. Additional Resources Red Hat Developer Toolset 1.x User Guide 5 4. binutils 4.1. Installing binutils 4.2. Using the GNU Assembler 4.3. Using the GNU Linker 4.4. Using Other Binary Tools 4.5. Additional Resources 5. elfutils 5.1. Installing elfutils 5.2. Using elfutils 5.3. Additional Resources 6. dwz 6.1. Installing dwz 6.2. Using dwz 6.3. Additional Resources III. Performance Monitoring Tools 7. SystemTap 7.1. Installing SystemTap 7.2. Using SystemTap 7.3. Additional Resources 8. Valgrind 8.1. Installing Valgrind 8.2. Using Valgrind 8.3. Additional Resources 9. OProfile 9.1. Installing OProfile 9.2. Using OProfile 9.3. Additional Resources IV. Integrated Development Environments 10. Eclipse 10.1. Installing Eclipse 10.2. Running Eclipse 10.3. Additional Resources V. Getting Help 11. Accessing Red Hat Product Documentation 12. Accessing the Customer Portal 12.1. The Plan Menu 12.2. The Deploy Menu 12.3. The Connect Menu 13. Contacting Global Support Services 13.1. Gathering Required Information 13.2. Escalating an Issue 13.3. Re-opening a Service Request 13.4. Additional Resources A. Changes in Version 1.0 A.1. Changes in GCC 4.7.0 6 Table of Contents A.1.1. Status and Features A.1.2. Language Compatibility A.1.3. ABI Compatibility A.1.4. Debugging Compatibility A.1.5. Other Compatibility A.2. Changes in GDB 7.4 A.2.1. New Features A.2.2. Compatibility Changes A.3. Changes in binutils 2.22.52 A.3.1. GNU Linker A.3.2. GNU Assembler A.3.3. Other Binary Tools B. Changes in Version 1.1 B.1. Changes in GCC 4.7.2 B.1.1. C++11 Compatibility B.1.2. Fortran B.1.3. Architecture-specific Options B.2. Changes in GDB 7.5 B.3. Changes in binutils 2.23.51 B.3.1. GNU Linker B.3.2. GNU Assembler B.3.3. Other Binary Tools B.4. Changes in elfutils 0.154 B.5. Changes in Valgrind 3.8.1 B.6. Changes in OProfile 0.154 C. Revision History Index Red Hat Developer Toolset 1.x User Guide 7 Preface 1. Document Conventions This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default. 1.1. Typographic Conventions Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows. Mono-spaced Bold Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example: To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command. The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context. Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example: Press Enter to execute the command. Press Ctrl+Alt+F2 to switch to a virtual terminal. The first example highlights a particular key to press. The second example highlights a key combination: a set of three keys pressed simultaneously. If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example: File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions. Proportional Bold This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example: Choose System → Preferences → Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). To insert a special character into a gedit file, choose Applications → Accessories → Character Map from the main menu bar. Next, choose Search → Find… from the 8 Preface Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit → Paste from the gedit menu bar. The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. Mono-spaced Bold Italic or Proportional Bold Italic Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: To connect to a remote machine using ssh, type ssh [email protected] at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh [email protected]. The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. To see the version of a currently installed package, use the rpm -q package command.
Recommended publications
  • Latent GOLD, Polca, and MCLUST

    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.
  • Embedded Linux Systems with the Yocto Project™

    Embedded Linux Systems with the Yocto Project™

    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
  • System Administration

    System Administration

    System Administration Varian NMR Spectrometer Systems With VNMR 6.1C Software Pub. No. 01-999166-00, Rev. C0503 System Administration Varian NMR Spectrometer Systems With VNMR 6.1C Software Pub. No. 01-999166-00, Rev. C0503 Revision history: A0800 – Initial release for VNMR 6.1C A1001 – Corrected errors on pg 120, general edit B0202 – Updated AutoTest B0602 – Added additional Autotest sections including VNMRJ update B1002 – Updated Solaris patch information and revised section 21.7, Autotest C0503 – Add additional Autotest sections including cryogenic probes Applicability: Varian NMR spectrometer systems with Sun workstations running Solaris 2.x and VNMR 6.1C software By Rolf Kyburz ([email protected]) Varian International AG, Zug, Switzerland, and Gerald Simon ([email protected]) Varian GmbH, Darmstadt, Germany Additional contributions by Frits Vosman, Dan Iverson, Evan Williams, George Gray, Steve Cheatham Technical writer: Mike Miller Technical editor: Dan Steele Copyright 2001, 2002, 2003 by Varian, Inc., NMR Systems 3120 Hansen Way, Palo Alto, California 94304 1-800-356-4437 http://www.varianinc.com All rights reserved. Printed in the United States. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies. Statements in this document are not intended to create any warranty, expressed or implied. Specifications and performance characteristics of the software described in this manual may be changed at any time without notice. Varian reserves the right to make changes in any products herein to improve reliability, function, or design. Varian does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under its patent rights nor the rights of others.
  • Rights Reserved. Permission to Make Digital Or Hard Copies of All Or Part Of

    Rights Reserved. Permission to Make Digital Or Hard Copies of All Or Part Of

    Copyright © 1994, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 Microsoft Windows NT And The Competition for Desktop Computing January 1994 Department ofElectrical Engineering and Computer Sciences University ofCalifornia Berkeley, California 94720 Abstract This report contains two papers, An Introduction to Microsoft Windows NT And Its Competitors, and The Status ofWindows NT and Its Competitors At The End of1993. The first paper, written in April 1993,presents an overview of the technology of Windows NT, and analyzes the competitors and competitive factors in the desktop operating system race.
  • The Library for System Solutions End User Interface Reference

    The Library for System Solutions End User Interface Reference

    The Library for System Solutions End User Interface Reference Document Number GG24-4107-00 July 1994 International Technical Support Organization Boca Raton Center Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xi. First Edition (July 1994) This edition applies to IBM and non-IBM products for End User Interface development. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1. If the form has been removed, comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. 91J Building 235-2 Internal Zip 4423 901 NW 51st Street Boca Raton, Florida 33431-1328 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Abstract This document is part of the Library for Systems Solutions, which is intended for professionals involved in defining solutions in the heterogeneous computing environments. The library consists of three types of documents: • Computing Technology • Function Reference • Technology Reference This document is the Function Reference book regarding End User Interface. The book consists of two parts.
  • R Pass by Reference

    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.
  • Compiling C++ Files & Declarations and Definitions

    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 ..
  • International Technical Support Organization Managing AIX V4 on PCI-Based RISC System/6000 Workstations (40P/43P) September 1995 Publication No

    International Technical Support Organization Managing AIX V4 on PCI-Based RISC System/6000 Workstations (40P/43P) September 1995 Publication No

    International Technical Support Organization SG24-2581-00 Managing AIX V4 on PCI-Based RISC System/6000 Workstations (40P/43P) September 1995 IBML International Technical Support Organization SG24-2581-00 Managing AIX V4 on PCI-Based RISC System/6000 Workstations (40P/43P) September 1995 Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xvii. First Edition (September 1995) This edition applies to the AIX Version 4.1.2 and AIX Version 4.1.3 operating system. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1. If the form has been removed, comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9 Building 821 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1995. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Abstract The RISC System/6000 family of products, typically based on the Microchannel bus architecture, has been expanded to include a new line of products based on the PowerPC microprocessor, the Peripheral Component Interconnect (PCI) bus architecture and the PowerPC Reference Platform Specification (PReP).
  • 0137017839.Pdf

    0137017839.Pdf

    Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus, and branding interests. For more information, please contact: U.S. Corporate and Government Sales (800) 382-3419 [email protected] For sales outside the United States, please contact: International Sales [email protected] Visit us on the Web: informit.com/aw Library of Congress Cataloging-in-Publication Data: Hallinan, Christopher. Embedded Linux primer : a practical real-world approach / Christopher Hallinan. p. cm. ISBN 978-0-13-701783-6 (hardback : alk. paper) 1. Linux. 2. Operating systems (Computers) 3. Embedded computer systems--Programming. I. Title. QA76.76.O63H34462 2011 005.4’32--dc22 2010032891 Copyright © 2011 Pearson Education, Inc. All rights reserved. Printed in the United States of America. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise.
  • Linuxvilag-56.Pdf 18399KB 43 2012-05-28 10:25:14

    Linuxvilag-56.Pdf 18399KB 43 2012-05-28 10:25:14

    Beköszöntõ © Kiskapu Kft. Minden jog fenntartva A Pingvin új ruhája tudjuk, hogy gyermekünk Alex Már-már a hazai hivatalokat legyen-e, vagy Tóbiás (akirõl nemrég is megszégyenítõ sebességgel, kiderült, hogy lehet, hogy lány). hosszadalmas háttérmunka Részletesebben a 17. oldalon! után, végre elérkezett az idõ, hogy a világ elé tárjuk a meg- Az új grafikai témájú sorozatok mel- újult Linuxvilágot! A változta- lett (Blender, POVRay, SVG) a mostani Szy György tások valószínûleg mindenki- számban közöljük le a Linux Journal fõszerkesztõ nek szembeötlõek lesznek, csapata által épített néma erõmûrõl bár bevallom, azon vélemé- szóló cikket is, a 24. oldalon. (Halló, nyemet, miszerint is jelenjen meg munkáltatók! Ma már nem luxus a lapban minél több szép lány, csak a csendes iroda!) És ha van egy szno- részben tudtam érvényesíteni. Fonto- bok számára is megfelelõ csúcsgé- sabb cél volt ugyanis, hogy olvasóink pünk, hát futtassunk rajta húsz-har- igénye szerint elsõsorban a tartalomra minc másikat! Ennek megoldásához helyezzük a hangsúlyt: kevesebb erõ- három módszert hasonlítunk össze, sen szakmai cikk, több érdekesség, a XEN, a vmWare és a Qemu progra- több hazai anyag. mok személyében (az összeállítás a 34. oldalon kezdõdik). Természetesen az új laptartalom mel- lett szerettük volna a linuxos közösség A temérdek változtatásról természete- által tiszteletnek örvendõ nemes tityi- sen szeretnénk minél több véleményt totyi állatkák elõtt is tisztelegni, ami- kapni, úgyhogy usgyi, a lap átolvasása hez a legjobb megoldást a Budapesti után mindenki
  • Case COMP/C-3/37.792 Microsoft)

    Case COMP/C-3/37.792 Microsoft)

    EN EN EN COMMISSION OF THE EUROPEAN COMMUNITIES Brussels, 21.4.2004 C(2004)900 final COMMISSION DECISION of 24.03.2004 relating to a proceeding under Article 82 of the EC Treaty (Case COMP/C-3/37.792 Microsoft) (ONLY THE ENGLISH TEXT IS AUTHENTIC) (Text with EEA relevance) EN EN COMMISSION DECISION of 24.03.2004 relating to a proceeding under Article 82 of the EC Treaty (Case COMP/C-3/37.792 Microsoft) (ONLY THE ENGLISH TEXT IS AUTHENTIC) (Text with EEA relevance) THE COMMISSION OF THE EUROPEAN COMMUNITIES, Having regard to the Treaty establishing the European Community, Having regard to Council Regulation No 17 of 6 February 1962, First Regulation implementing Articles 85 and 86 of the Treaty1, and in particular Article 3 and Article 15(2) thereof, Having regard to the complaint lodged by Sun Microsystems, Inc. on 10 December 1998, alleging infringements of Article 82 of the Treaty by Microsoft and requesting the Commission to put an end to those infringements, Having regard to the Commission decision of 1 August 2000 to initiate proceedings in Case IV/C-3/37.345, Having regard to the Commission decision of 29 August 2001 to initiate proceedings in this case, and to join the findings in Case IV/C-3/37.345 to the procedure followed under this case, Having given the undertaking concerned the opportunity to make known their views on the objections raised by the Commission pursuant to Article 19(1) of Regulation No 17 and Commission Regulation (EC) No 2842/98 of 22 December 1998 on the hearing of parties in certain proceedings under Articles 85 and 86 of the EC Treaty2, Having regard to the final report of the hearing officer in this case, After consulting the Advisory Committee on Restrictive Practices and Dominant Positions, 1 OJ 13, 21.2.1962, p.
  • Khem Raj Khem@Himvis.Com Embedded Linux Conference 2014, San Jose, CA

    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