DOCSLIB.ORG

Victor Stinner's Notes Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Victor Stinner's Notes Documentation Victor Stinner’s Notes Documentation Release 1.0 Victor Stinner Sep 22, 2021 Contents 1 My Projects 3 2 Talks 5 3 Old Projects (2000-2009) 11 4 Victor Stinner: Contact Me 15 5 My contributions to Python 19 6 My Contributions to Free Softwares 25 7 Analyze of PyPy warmup in performance benchmarks 31 8 C programming language 73 9 Unicode 81 10 Multithreading Programming 87 11 Benchmarks 91 12 FreeBSD 97 13 Survivor Guide to Develop on Windows 101 14 GDB: GNU debugger 109 15 Unsorted Notes 117 16 Inspect an ELF binary file 131 17 systemd 133 18 Python in Fedora 139 19 Red Hat and Python 141 20 Fedora 143 i 21 GNOME and Wayland 147 22 vim for developer 153 23 Assembly Intel x86 155 24 See also 157 25 Indices and tables 159 Index 161 ii Victor Stinner’s Notes Documentation, Release 1.0 Contents: Contents 1 Victor Stinner’s Notes Documentation, Release 1.0 2 Contents CHAPTER 1 My Projects Projects of Victor Stinner. See also: My talks, my contributions to Free Softwares and my old projects. 1.1 Websites • Python Development (created in Juny 2018) • Victor Stinner’s Blog 3 (new blog, created in 2015) • Victor Stinner’s Notes (this site, created in 2014) 3 Victor Stinner’s Notes Documentation, Release 1.0 1.2 Documentation • Faster CPython (source code: faster_cpython at github) • Programming with Unicode (source code: unicode_book at github) 1.3 Python Projects • fatoptimizer: static optimizer for Python 3.6 using function specialization with guards. It is implemented as an AST optimizer. It is part of the FAT Python project. • bytecode: API to modify Python bytecode, and a peephole optimizer. • pyfailmalloc: Debug tool for Python injecting memory allocation faults to simulate a low memory system to test how your application handles MemoryError exceptions. • sixer: add Python 3 support to Python 2 applications using the six module. • Hachoir: Python library that allows to view and edit a binary stream field by field. In other words, Hachoir allows you to “browse” any binary stream just like you browse directories and files. A file is split in a tree of fields, where the smallest field is just one bit. 1.4 Other Projects • “misc” repository: – my “dot” files, configuration files: bashrc, hgrc, gitconfig, etc. – some command line program: apply_patch.py, scm.py – some Python scripts – some shell scripts: apt_get.sh, fedora_new_install.sh 4 Chapter 1. My Projects CHAPTER 2 Talks See also my projects and my old projects. All my talks at available at Github: vstinner/conf. 2.1 Conferences 2011-today • May 2020, Pycon US, Online (because of the COVID-19) – Python Steering Council Community Address: Brett Cannon, Barry Warsaw, Carol Willing, Thomas Woul- ters, Victor Stinner. • July 2019, EuroPython at Basel (Switzerland) – “Python Performance: Past, Present and Future” keynote – Slides – Video (9h YouTube video, link to the start of the my talk, at 31:15) • May 2019, Python Language Summit (during Pycon US) at Cleveland (Ohio, USA) – Python Core Developer Mentorship with Chery Sabella and Pablo Galindo Salgado – slides • May 2019, Python Language Summit (during Pycon US) at Cleveland (Ohio, USA) 5 Victor Stinner’s Notes Documentation, Release 1.0 – Status of stable API and stable ABI in Python 3.8: lightning talk (5 min) • May 2019, Pycon US at Cleveland (Ohio, USA) – How to engage Python contributors in the long term? Tech is easy, people are hard. – video on Youtube – slides (PDF) • January 2019, Devconf.CZ at Brno (Czech Republic) – Howto engage Python contributors in the long term? – slides (PDF) • October 2018, Pycon FR at Lille (France) – Comment avoir plus de contributeurs à Python: PDF slides – Comment avoir plus de contributeurs à Python: video on Youtube, the video has subtitles in french (you can enable automatic translation to english, or maybe other languages) • July 2018, EuroPython at Edinburgh, Scotland, UK (keynote) – Python 3: ten years later. (same talk than FOSDEM 2018) • June 2018, PyLondonium at London, UK (keynote) – Python 3: ten years later. (same talk than FOSDEM 2018) • May 2018, Pycon US at Cleveland, Ohio, USA: 3 talks! – Python 3: ten years later (same talk than FOSDEM 2018): slides (PDF) and Youtube video – Mentoring and diversity for Python: slides (PDF) and LWN article. I focused on contributors and mentor- ing, then Mariatta Wijaya talked about diversity. – Stable ABI (slides, PDF) • April 2018, Pycon Italy at Firenze (keynote) – Python 3, ten years later: keynote. (same talk than FOSDEM 2018) • February 2018, FOSDEM at Brussels – Looking back at Python evolutions of the last 10 years – Slides (PDF) – Sorry for the bad sound in the video, there was an issue with sound during my talk and the video team and only fixed it after my talk: “we had some issues with microphone charging cables and other sillyness at some point”. • May 2017, Pycon US at Portland (Oregon, USA) – LWN article: Making Python faster – Talk: Optimizations which made Python 3.6 faster than Python 3.5 – Video (Youtube) – Slides (PDF): Optimizations which made Python 3.6 faster than Python 3.5 • May 2017, Language Summit during Pycon US at Portland (Oregon, USA) – LWN article: Keeping Python competitive – Talk: Python performance 6 Chapter 2. Talks Victor Stinner’s Notes Documentation, Release 1.0 – Slides (PDF): Python performance • February 2017, FOSDEM at Brussels (Belgium) – Video: How to run a stable benchmark – Slides (PDF): How to run stable benchmarks • July 2016, EuroPython at Bilbao (Spain) – Slides (PDF): FAT Python, a new static optimizer for CPython 3.6 – Video on Youtube: Victor Stinner - FAT Python: a new static optimizer for Python 3.6 • February 2016, FOSDEM at Brussels (Belgium): – Slides: FAT Python: New static optimizer for CPython 3.6 – website – (video lost, sorry) • 2015, /var/var at Toulon (France: – slides: (fr) Projet FAT Python: Optimiseur statique pour Python • 2015, EuroPython at Bilbao (Spain): – asyncio community, one year later – slides (PDF)(copy at europython website) – slides at slideshare • 2014, Pycon FR at Lyon (France): – Exploration de la boucle d’événements asyncio – slides (PDF) – slides at SpeackerDeck – video • 2014, Pycon “US” at Montréal (Canada): – Track memory leaks in Python – slides (PDF) – slides at SpeakerDeck – video • 2013, Pycon FR at Strasbourg (France): “Traquer les fuites mémoires Python” – slides (PDF) – slides at slideshare – video • 2013, FOSDEM at Brussels (Belgium): “Two projects to optimize Python” (astoptimizer, register-based byte- code) – slides (PDF) – slides at slideshare • 2012, Pycon FR at Paris (France): 2.1. Conferences 2011-today 7 Victor Stinner’s Notes Documentation, Release 1.0 – Processus de développement de CPython – Nouveautés de Python 3.3 • 2011, Pycon US at Atlanta (USA): – https://github.com/vstinner/talks/tree/master/2011-PyconUS-Atlanta – video (blip.tv) – video (pyvideo) • 2011, Pycon FR at Rennes (France): – “Développement de CPython”: * slides (PDF) * slides at slideshare – Python : langage homogène, explicite et efficace 2.2 Conferences 2005-2009 • 2009, Pycon FR at Paris (France): – Comprendre les erreurs Unicode: slides, video – Contribuer à Python – Python bling bling: slides, video – Interview of myself • 2009, OSDC at Paris (France): – Génerer des nombres aléatoires avec Hasard. • 2009: FOSDEM at Brussels (Belgium): – Fusil the fuzzer – Video of the demo (fusil-python.ogg) – Video: FOSDEM 2009 Fusil fuzzing • 2008, RMLL at Mont de Marsan (France): – Assurance qualité avec Fusil le fuzzer – https://github.com/vstinner/talks/tree/master/2008-RMLL • 2008, Pycon FR at Paris (France): – PyPy – PyPy: video – Python 3 aka “Pytho 3000” – Python 3: video • 2007, SSTIC at Rennes (France): – Project Fusil • 2007, Pycon FR at Paris (France): https://github.com/vstinner/talks/tree/master/2007-Pycon-Paris 8 Chapter 2. Talks Victor Stinner’s Notes Documentation, Release 1.0 • January 2007, AAM (Appel À Mousser) at Strasbourg (France): – Hachoir • 2005, UTBM at Belfort (France), Lolut association: Atelier sécurite PHP and MySQL – PHP “crackme” exercices: vulnerable PHP pages – Failles en PHP et injection SQL • 2005, UTBM at Belfort (France), Lolut association: Atelier sécurité of C programming – Introduction générale à la sécurité informatique (french) – Mots de passe, chiffrement et signature – Aide-mémoire sur les failles en C – C exercices: vulnerable C programs • 2005, Gameover at Limoges (France): – Wormux (french), conference given with Lawrence Azzoug. 2.2. Conferences 2005-2009 9 Victor Stinner’s Notes Documentation, Release 1.0 10 Chapter 2. Talks CHAPTER 3 Old Projects (2000-2009) See also: My current projects and my talks. 3.1 Websites • La page de Haypo (2005) • Turbo Pascal (2004) 11 Victor Stinner’s Notes Documentation, Release 1.0 3.2 Old websites (dead) • Wiki (last new article in december 2013). • Blog Haypo (last article in 2011) • Wordpress Blog (dead URL: http://www.haypocalc.com/wordpress/) (last article in 2011) These sites were hosted at the haypocalc.com domain created in december 2001, but the domain died in december 2017, 16 years later. 3.3 Articles on linuxfr.org Some of my articles: • Python 3.4 est sorti avec 7 nouveaux modules (2014/03) • Justice Free publie enfin ses patchs sur les logiciels libres (2011/09) • Python 3.2 (2011/02) • Patch pour le noyau Linux améliorant l’interactivité entre les applications console et Xorg (2010/11) • Python 2.7 (2010/07) • Sortie de la version 2.11 de la bibliothèque standard C GNU (glibc) (2009/11) • Intel ne maintient plus le pilote Linux Poulsbo depuis un an et demi (2009/10) • Python arrive en version 3.1 (2009/07) • Debian remplace la glibc par eglibc (2009/05) • Nouvelle version majeure de Python (2.6) (2008/10) 3.4 Paper Articles • Netfilter et le filtrage du protocole IPv6 (french): GNU/Linux Magazine HS 41 (April 2009) • Hors-série Linux Mag : Explorez les richesses du langage Python (january/february 2009). I wrote 4 articles: – Nouveautés de Python 2.6 – Nouveautés de Python 3.0 – Trucs et astuces – Ctypes et Python • “Pratique du fuzzing avec Fusil” (french), MISC magazine n°39 (september 2008) • Comment réaliser un fuzzer ? (french), MISC magazine n°36 (march 2008) 3.5 Python projects • pytracemalloc: debug tool to trace memory blocks allocated by Python.
Load more

Recommended publications
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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.
    [Show full text]
  • Common Tools for Team Collaboration Problem: Working with a Team (Especially Remotely) Can Be Difficult
    Common Tools for Team Collaboration Problem: Working with a team (especially remotely) can be difficult. ▹ Team members might have a different idea for the project ▹ Two or more team members could end up doing the same work ▹ Or a few team members have nothing to do Solutions: A combination of few tools. ▹ Communication channels ▹ Wikis ▹ Task manager ▹ Version Control ￭ We’ll be going in depth with this one! Important! The tools are only as good as your team uses them. Make sure all of your team members agree on what tools to use, and train them thoroughly! Communication Channels Purpose: Communication channels provide a way to have team members remotely communicate with one another. Ideally, the channel will attempt to emulate, as closely as possible, what communication would be like if all of your team members were in the same office. Wait, why not email? ▹ No voice support ￭ Text alone is not a sufficient form of communication ▹ Too slow, no obvious support for notifications ▹ Lack of flexibility in grouping people Tools: ▹ Discord ￭ discordapp.com ▹ Slack ￭ slack.com ▹ Riot.im ￭ about.riot.im Discord: Originally used for voice-chat for gaming, Discord provides: ▹ Voice & video conferencing ▹ Text communication, separated by channels ▹ File-sharing ▹ Private communications ▹ A mobile, web, and desktop app Slack: A business-oriented text communication that also supports: ▹ Everything Discord does, plus... ▹ Threaded conversations Riot.im: A self-hosted, open-source alternative to Slack Wikis Purpose: Professionally used as a collaborative game design document, a wiki is a synchronized documentation tool that retains a thorough history of changes that occured on each page.
    [Show full text]
  • Microcode Revision Guidance August 31, 2019 MCU Recommendations
    microcode revision guidance August 31, 2019 MCU Recommendations Section 1 – Planned microcode updates • Provides details on Intel microcode updates currently planned or available and corresponding to Intel-SA-00233 published June 18, 2019. • Changes from prior revision(s) will be highlighted in yellow. Section 2 – No planned microcode updates • Products for which Intel does not plan to release microcode updates. This includes products previously identified as such. LEGEND: Production Status: • Planned – Intel is planning on releasing a MCU at a future date. • Beta – Intel has released this production signed MCU under NDA for all customers to validate. • Production – Intel has completed all validation and is authorizing customers to use this MCU in a production environment.
    [Show full text]
  • Sistemas De Control De Versiones De Última Generación (DCA)
    Tema 10 - Sistemas de Control de Versiones de última generación (DCA) Antonio-M. Corbí Bellot Tema 10 - Sistemas de Control de Versiones de última generación (DCA) II HISTORIAL DE REVISIONES NÚMERO FECHA MODIFICACIONES NOMBRE Tema 10 - Sistemas de Control de Versiones de última generación (DCA) III Índice 1. ¿Qué es un Sistema de Control de Versiones (SCV)?1 2. ¿En qué consiste el control de versiones?1 3. Conceptos generales de los SCV (I) 1 4. Conceptos generales de los SCV (II) 2 5. Tipos de SCV. 2 6. Centralizados vs. Distribuidos en 90sg 2 7. ¿Qué opciones tenemos disponibles? 2 8. ¿Qué podemos hacer con un SCV? 3 9. Tipos de ramas 3 10. Formas de integrar una rama en otra (I)3 11. Formas de integrar una rama en otra (II)4 12. SCV’s con los que trabajaremos 4 13. Git (I) 5 14. Git (II) 5 15. Git (III) 5 16. Git (IV) 6 17. Git (V) 6 18. Git (VI) 7 19. Git (VII) 7 20. Git (VIII) 7 21. Git (IX) 8 22. Git (X) 8 23. Git (XI) 9 Tema 10 - Sistemas de Control de Versiones de última generación (DCA) IV 24. Git (XII) 9 25. Git (XIII) 9 26. Git (XIV) 10 27. Git (XV) 10 28. Git (XVI) 11 29. Git (XVII) 11 30. Git (XVIII) 12 31. Git (XIX) 12 32. Git. Vídeos relacionados 12 33. Mercurial (I) 12 34. Mercurial (II) 12 35. Mercurial (III) 13 36. Mercurial (IV) 13 37. Mercurial (V) 13 38. Mercurial (VI) 14 39.
    [Show full text]
  • Class-Action Lawsuit
    Case 3:20-cv-00863-SI Document 1 Filed 05/29/20 Page 1 of 279 Steve D. Larson, OSB No. 863540 Email: [email protected] Jennifer S. Wagner, OSB No. 024470 Email: [email protected] STOLL STOLL BERNE LOKTING & SHLACHTER P.C. 209 SW Oak Street, Suite 500 Portland, Oregon 97204 Telephone: (503) 227-1600 Attorneys for Plaintiffs [Additional Counsel Listed on Signature Page.] UNITED STATES DISTRICT COURT DISTRICT OF OREGON PORTLAND DIVISION BLUE PEAK HOSTING, LLC, PAMELA Case No. GREEN, TITI RICAFORT, MARGARITE SIMPSON, and MICHAEL NELSON, on behalf of CLASS ACTION ALLEGATION themselves and all others similarly situated, COMPLAINT Plaintiffs, DEMAND FOR JURY TRIAL v. INTEL CORPORATION, a Delaware corporation, Defendant. CLASS ACTION ALLEGATION COMPLAINT Case 3:20-cv-00863-SI Document 1 Filed 05/29/20 Page 2 of 279 Plaintiffs Blue Peak Hosting, LLC, Pamela Green, Titi Ricafort, Margarite Sampson, and Michael Nelson, individually and on behalf of the members of the Class defined below, allege the following against Defendant Intel Corporation (“Intel” or “the Company”), based upon personal knowledge with respect to themselves and on information and belief derived from, among other things, the investigation of counsel and review of public documents as to all other matters. INTRODUCTION 1. Despite Intel’s intentional concealment of specific design choices that it long knew rendered its central processing units (“CPUs” or “processors”) unsecure, it was only in January 2018 that it was first revealed to the public that Intel’s CPUs have significant security vulnerabilities that gave unauthorized program instructions access to protected data. 2. A CPU is the “brain” in every computer and mobile device and processes all of the essential applications, including the handling of confidential information such as passwords and encryption keys.
    [Show full text]
  • Useful Tools for Game Making
    CMS.611J/6.073 Fall 2014 Useful Tools List This list is by no means complete, but should get you started. Talk to other folks in the class about their recommendations. Revision Control Version control software, provides backups and easy reversion. Perforce Mac/Win GUI (p4v): Heavily used in game http://www.perforce.com/dow industry. Commercial nloads/Perforce-Software-Ver software; you can use the sion-Management/complete_l Game Lab server. ist/Customer Subversion Command line: Open source, server-based http://subversion.apache.org/ Windows GUI: http://tortoisesvn.net/ Git Command line: Open source, distributed http://git-scm.com/ Mercurial Command line: Open source, distributed http://mercurial.selenic.com/ Windows GUI: http://tortoisehg.bitbucket.org/ SourceTree Mac/Win GUI: Not a source control system, http://www.sourcetreeapp.co just a GUI for Git and m/ Mercurial clients Revision Control Hosting SourceForge http://sourceforge.net/ git, mercurial, or subversion BitBucket https://bitbucket.org/ git or mercurial GitHub https://github.com/ git, has own (painful) GUI for Git 1 Image Editing MSPaint Windows, pre-installed Surprisingly useful quick pixel art editor (esp for prototypes) Paint.NET Windows, About as easy as MSPaint, but http://www.getpaint.net/download much more powerful .html Photoshop Mac, Windows New Media Center, 26-139 GIMP Many platforms, Easier than photoshop, at http://www.gimp.org/downloads/ least. Sound GarageBand Mac New Media Center, 26-139 Audacity Many platforms, Free, open source. http://audacity.sourceforge.ne
    [Show full text]
  • Multiprocessing Contents
    Multiprocessing Contents 1 Multiprocessing 1 1.1 Pre-history .............................................. 1 1.2 Key topics ............................................... 1 1.2.1 Processor symmetry ...................................... 1 1.2.2 Instruction and data streams ................................. 1 1.2.3 Processor coupling ...................................... 2 1.2.4 Multiprocessor Communication Architecture ......................... 2 1.3 Flynn’s taxonomy ........................................... 2 1.3.1 SISD multiprocessing ..................................... 2 1.3.2 SIMD multiprocessing .................................... 2 1.3.3 MISD multiprocessing .................................... 3 1.3.4 MIMD multiprocessing .................................... 3 1.4 See also ................................................ 3 1.5 References ............................................... 3 2 Computer multitasking 5 2.1 Multiprogramming .......................................... 5 2.2 Cooperative multitasking ....................................... 6 2.3 Preemptive multitasking ....................................... 6 2.4 Real time ............................................... 7 2.5 Multithreading ............................................ 7 2.6 Memory protection .......................................... 7 2.7 Memory swapping .......................................... 7 2.8 Programming ............................................. 7 2.9 See also ................................................ 8 2.10 References .............................................
    [Show full text]
  • Hg Mercurial Cheat Sheet Serge Y
    Hg Mercurial Cheat Sheet Serge Y. Stroobandt Copyright 2013–2020, licensed under Creative Commons BY-NC-SA #This page is work in progress! Much of the explanatory text still needs to be written. Nonetheless, the basic outline of this page may already be useful and this is why I am sharing it. In the mean time, please, bare with me and check back for updates. Distributed revision control Why I went with Mercurial • Python, Mozilla, Java, Vim • Mercurial has been better supported under Windows. • Mercurial also offers named branches Emil Sit: • August 2008: Mercurial offers a comfortable command-line experience, learning Git can be a bit daunting • December 2011: Git has three “philosophical” distinctions in its favour, as well as more attention to detail Lowest common denominator It is more important that people start using dis- tributed revision control instead of nothing at all. The Pro Git book is available online. Collaboration styles • Mercurial working practices • Collaborating with other people Use SSH shorthand 1 Installation $ sudo apt-get update $ sudo apt-get install mercurial mercurial-git meld Configuration Local system-wide configuration $ nano .bashrc export NAME="John Doe" export EMAIL="[email protected]" $ source .bashrc ~/.hgrc on a client user@client $ nano ~/.hgrc [ui] username = user@client editor = nano merge = meld ssh = ssh -C [extensions] convert = graphlog = mq = progress = strip = 2 ~/.hgrc on the server user@server $ nano ~/.hgrc [ui] username = user@server editor = nano merge = meld ssh = ssh -C [extensions] convert = graphlog = mq = progress = strip = [hooks] changegroup = hg update >&2 Initiating One starts with initiate a new repository.
    [Show full text]
  • The Intel X86 Microarchitectures Map Version 2.0
    The Intel x86 Microarchitectures Map Version 2.0 P6 (1995, 0.50 to 0.35 μm) 8086 (1978, 3 µm) 80386 (1985, 1.5 to 1 µm) P5 (1993, 0.80 to 0.35 μm) NetBurst (2000 , 180 to 130 nm) Skylake (2015, 14 nm) Alternative Names: i686 Series: Alternative Names: iAPX 386, 386, i386 Alternative Names: Pentium, 80586, 586, i586 Alternative Names: Pentium 4, Pentium IV, P4 Alternative Names: SKL (Desktop and Mobile), SKX (Server) Series: Pentium Pro (used in desktops and servers) • 16-bit data bus: 8086 (iAPX Series: Series: Series: Series: • Variant: Klamath (1997, 0.35 μm) 86) • Desktop/Server: i386DX Desktop/Server: P5, P54C • Desktop: Willamette (180 nm) • Desktop: Desktop 6th Generation Core i5 (Skylake-S and Skylake-H) • Alternative Names: Pentium II, PII • 8-bit data bus: 8088 (iAPX • Desktop lower-performance: i386SX Desktop/Server higher-performance: P54CQS, P54CS • Desktop higher-performance: Northwood Pentium 4 (130 nm), Northwood B Pentium 4 HT (130 nm), • Desktop higher-performance: Desktop 6th Generation Core i7 (Skylake-S and Skylake-H), Desktop 7th Generation Core i7 X (Skylake-X), • Series: Klamath (used in desktops) 88) • Mobile: i386SL, 80376, i386EX, Mobile: P54C, P54LM Northwood C Pentium 4 HT (130 nm), Gallatin (Pentium 4 Extreme Edition 130 nm) Desktop 7th Generation Core i9 X (Skylake-X), Desktop 9th Generation Core i7 X (Skylake-X), Desktop 9th Generation Core i9 X (Skylake-X) • Variant: Deschutes (1998, 0.25 to 0.18 μm) i386CXSA, i386SXSA, i386CXSB Compatibility: Pentium OverDrive • Desktop lower-performance: Willamette-128
    [Show full text]
  • Mutter 3.27.1
    GNOME.org Home Mailing Lists List Archives Search Mutter 3.27.1 From: Florian Müllner <fmuellner gnome org> To: gnome-shell-list <gnome-shell-list gnome org>, gnome-announce-list <gnome-announce-list gnome org> Subject: Mutter 3.27.1 Date: Tue, 17 Oct 2017 18:12:55 +0200 About mutter ============ Mutter is a window and compositing manager that displays and manages your desktop via OpenGL. Mutter combines a sophisticated display engine using the Clutter toolkit with solid window-management logic inherited from the Metacity window manager. While Mutter can be used stand-alone, it is primarily intended to be used as the display core of a larger system such as GNOME Shell. For this reason, Mutter is very extensible via plugins, which are used both to add fancy visual effects and to rework the window management behaviors to meet the needs of the environment. News ==== * Work with clients that require older linux_dmabuf protocol [Daniel; #788558] * Support hybrid GPU systems [Jonas; #785381] * Prevent crash when closing maximized windows [Jonni; #788666] * Use the correct monitor for HiDPI scaling of shell chrome [Jonas; #788820] * Fix unredirection of fullscreen windows [Rui, Jonas; #788493] * Fix list of supported monitor scales on X11 [Jonas; #788901] * Misc. bug fixes [Florian, Jonas, Marco; #788572, #788569, #788607, #788860, #788921] Contributors: Jonas Ådahl, Carlos Garnacho, Rui Matos, Florian Müllner, Daniel Stone, Marco Trevisan, Jonni Westphalen Translations: Xavi Ivars [ca@valencia] Download ======== https://download.gnome.org/sources/mutter/3.27/mutter-3.27.1.tar.xz
    [Show full text]
  • Informatyka 1, Studia Niestacjonarne I Stopnia Dr Inż
    Informatyka 1, studia niestacjonarne I stopnia dr inż. Jarosław Forenc Rok akademicki 2018/2019, Wykład nr 5 2/59 Plan wykładu nr 5 Informatyka 1 Język C § pętla for, operatory ++ i – Klasyfikacja systemów komputerowych (Flynna) Architektura von Neumanna i architektura harwardzka Politechnika Białostocka --WydziałWydział Elektryczny Budowa komputera § jednostka centralna Elektrotechnika, semestr II, studia niestacjonarne I stopnia § płyta główna Rok akademicki 2018/2019 § procesor (mikroarchitektury) Wykład nr 5 (05.04.2019) dr inż. Jarosław Forenc Informatyka 1, studia niestacjonarne I stopnia dr inż. Jarosław Forenc Informatyka 1, studia niestacjonarne I stopnia dr inż. Jarosław Forenc Rok akademicki 2018/2019, Wykład nr 5 3/59 Rok akademicki 2018/2019, Wykład nr 5 4/59 Język C --sumasuma kolejnych 10 liczb: 1+2+…+10 Język C --sumasuma kolejnych 100 liczb: 1+2+…+100 Suma wynosi: 55 Suma wynosi: 5050 #include <stdio.h> #include <stdio.h> int main(void ) int main(void ) { { int suma; int suma=0, i; suma = 1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10; for (i=1; i<=100; i=i+1) suma = suma + i; printf("Suma wynosi: %d\n" ,suma); printf("Suma wynosi: %d\n" ,suma); return 0; } return 0; } Informatyka 1, studia niestacjonarne I stopnia dr inż. Jarosław Forenc Informatyka 1, studia niestacjonarne I stopnia dr inż. Jarosław Forenc Rok akademicki 2018/2019, Wykład nr 5 5/59 Rok akademicki 2018/2019, Wykład nr 5 6/59 Język C --pętlapętla for Język C --pętlapętla for Najczęściej stosowana postać pętli for for (wyr1; wyr2; wyr3) wyr1 instrukcja int i; for (i = 0; i < 10; i = i + 1) NIE wyr 2 ≠ 0 instrukcja wyr1 , wyr2 , wyr3 - dowolne wyrażenia w języku C TAK Instrukcja zostanie wykonana 10 razy Instrukcja: instrukcja (dla i = 0, 1, 2, … 9 ) § prosta - jedna instrukcja Funkcje pełnione przez wyrażenia zakończona średnikiem wyr3 § złożona - jedna lub kilka instrukcji objętych nawiasami klamrowymi for (inicjalizacja ;test ;aktualizacja ) instrukcja Informatyka 1, studia niestacjonarne I stopnia dr inż.
    [Show full text]
  • NA-42 TI Shared Software Component Library FY2011 Final Report
    PNNL-20567 Prepared for the U.S. Department of Energy under Contract DE-AC05-76RL01830 NA-42 TI Shared Software Component Library FY2011 Final Report CK Knudson FC Rutz KE Dorow July 2011 DISCLAIMER This report was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor any agency thereof, nor Battelle Memorial Institute, nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof, or Battelle Memorial Institute. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. PACIFIC NORTHWEST NATIONAL LABORATORY operated by BATTELLE for the UNITED STATES DEPARTMENT OF ENERGY under Contract DE-AC05-76RL01830 Printed in the United States of America Available to DOE and DOE contractors from the Office of Scientific and Technical Information, P.O. Box 62, Oak Ridge, TN 37831-0062; ph: (865) 576-8401 fax: (865) 576-5728 email: [email protected] Available to the public from the National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Rd., Springfield, VA 22161 ph: (800) 553-6847 fax: (703) 605-6900 email: [email protected] online ordering: http://www.ntis.gov/ordering.htm This document was printed on recycled paper.
    [Show full text]