DOCSLIB.ORG

17-355/17-665: Program Analysis

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
17-355/17-665: Program Analysis 17-355/17-665: Program Analysis Introduction to Program Analysis Jonathan Aldrich Introduction 17-355/17-665: Program Analysis 1 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Find the Bug! Compiler Extensions, OSDI ’00. disable interrupts re-enable interrupts Introduction 17-355/17-665: Program Analysis 2 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Find the Bug! Compiler Extensions, OSDI ’00. disable interrupts ERROR: returning with interrupts disabled re-enable interrupts Introduction 17-355/17-665: Program Analysis 3 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. Introduction 17-355/17-665: Program Analysis 4 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. is_enabled Introduction 17-355/17-665: Program Analysis 5 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. is_enabled disable is_disabled Introduction 17-355/17-665: Program Analysis 6 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. enable => err(double enable) is_enabled disable is_disabled Introduction 17-355/17-665: Program Analysis 7 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. enable => err(double enable) is_enabled enable disable is_disabled Introduction 17-355/17-665: Program Analysis 8 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. enable => err(double enable) is_enabled enable disable is_disabled disable => err(double disable) Introduction 17-355/17-665: Program Analysis 9 © 2017 Jonathan Aldrich Metal Interrupt Analysis Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions, OSDI ’00. enable => err(double enable) is_enabled enable disable is_disabled end path => err(end path with/intr disabled) disable => err(double disable) Introduction 17-355/17-665: Program Analysis 10 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. Introduction 17-355/17-665: Program Analysis 11 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. initial state is_enabled Introduction 17-355/17-665: Program Analysis 12 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. initial state is_enabled transition to is_disabled Introduction 17-355/17-665: Program Analysis 13 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. initial state is_enabled transition to is_disabled final state is_disabled: ERROR! Introduction 17-355/17-665: Program Analysis 14 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. initial state is_enabled transition to is_disabled final state is_disabled: ERROR! transition to is_enabled Introduction 17-355/17-665: Program Analysis 15 © 2017 Jonathan Aldrich Source: Engler et al., Checking System Rules Using System-Specific, Programmer-Written Applying the Analysis Compiler Extensions, OSDI ’00. initial state is_enabled transition to is_disabled final state is_disabled: ERROR! transition to is_enabled final state is_enabled is OK Introduction 17-355/17-665: Program Analysis 16 © 2017 Jonathan Aldrich Outline • Why program analysis? • The limits of testing and inspection • What is program analysis? • Course outline • Representing programs • AST-walking analyses Introduction 17-355/17-665: Program Analysis 17 © 2017 Jonathan Aldrich Introduction 17-355/17-665: Program Analysis 18 © 2017 Jonathan Aldrich Static Analysis Finds “Mechanical” Errors • Defects that result from inconsistently following simple, mechanical design rules • Security vulnerabilities • Buffer overruns, unvalidated input… • Memory errors • Null dereference, uninitialized data… • Resource leaks • Memory, OS resources… • Violations of API or framework rules • e.g. Windows device drivers; real time libraries; GUI frameworks • Exceptions • Arithmetic/library/user-defined • Encapsulation violations • Accessing internal data, calling private functions… • Race conditions • Two threads access the same data without synchronization Introduction 17-355/17-665: Program Analysis 19 © 2017 Jonathan Aldrich Difficult to Find with Testing, Inspection • Non-local, uncommon paths • Security vulnerabilities • Memory errors • Resource leaks • Violations of API or framework rules • Exceptions • Encapsulation violations • Non-deterministic • Race conditions Introduction 17-355/17-665: Program Analysis 20 © 2017 Jonathan Aldrich Quality Assurance at Microsoft (Part 1) • Original process: manual code inspection • Effective when system and team are small • Too many paths to consider as system grew Early 1990s: add massive system and unit testing Tests took weeks to run Diversity of platforms and configurations Sheer volume of tests Inefficient detection of common patterns, security holes Non-local, intermittent, uncommon path bugs Was treading water in Windows Vista development Early 2000s: add static analysis More on this later Introduction 17-355/17-665: Program Analysis 21 © 2017 Jonathan Aldrich Quality Assurance at Microsoft (Part 1) • Original process: manual code inspection • Effective when system and team are small • Too many paths to consider as system grew • Early 1990s: add massive system and unit testing • Tests took weeks to run • Diversity of platforms and configurations • Sheer volume of tests • Inefficient detection of common patterns, security holes • Non-local, intermittent, uncommon path bugs • Was treading water in Windows Vista development Early 2000s: add static analysis More on this later Introduction 17-355/17-665: Program Analysis 22 © 2017 Jonathan Aldrich Quality Assurance at Microsoft (Part 1) • Original process: manual code inspection • Effective when system and team are small • Too many paths to consider as system grew • Early 1990s: add massive system and unit testing • Tests took weeks to run • Diversity of platforms and configurations • Sheer volume of tests • Inefficient detection of common patterns, security holes • Non-local, intermittent, uncommon path bugs • Was treading water in Windows Vista development • Early 2000s: add program analysis • More on this later Introduction 17-355/17-665: Program Analysis 23 © 2017 Jonathan Aldrich Process, Cost, and Quality Slide: William Scherlis Process intervention, Additional technology testing, and inspection and tools are needed to yield first-order close the gap software quality improvement Perfection (unattainable) Critical Systems Acceptability Software Quality Process CMM: 1 2 3 4 5 Rigor, Cost S&S, Agile, RUP, etc: less rigorous . more rigorous Introduction 17-355/17-665: Program Analysis 24 © 2017 Jonathan Aldrich Outline • Why static analysis? • What is static analysis? • Abstract state space exploration • Course outline • Representing programs • AST-walking analyses Introduction 17-355/17-665: Program Analysis 25 © 2017 Jonathan Aldrich Static Program Analysis Definition • Static program analysis is the automated, systematic examination of an abstraction of a program’s state space Introduction 17-355/17-665: Program Analysis 26 © 2017 Jonathan Aldrich Static Program Analysis Definition • Static program analysis is the automated, systematic examination of an abstraction of a program’s state space • Metal interrupt analysis • Abstraction • 2 states: enabled and disabled • All program information—variable values, heap contents—is abstracted by these two states, plus the program counter Introduction 17-355/17-665: Program Analysis 27 © 2017 Jonathan Aldrich Static Program Analysis Definition • Static program analysis is the automated, systematic examination of an abstraction of a program’s state space • Metal interrupt analysis • Abstraction • 2 states: enabled and disabled • All program information—variable values, heap contents—is abstracted by these two states, plus the program counter • Systematic • Examines all paths through a function • What about loops? More later… • Each path explored for each reachable state • Assume interrupts initially enabled (Linux practice) • Since the two states abstract all program information, the exploration is exhaustive Introduction 17-355/17-665: Program Analysis 28 © 2017 Jonathan Aldrich Static Program Analysis Definition • Static program analysis is the automated, systematic examination of an abstraction of a program’s state space • Mathematical properties (recurring theme) • Soundness • All reported results are true • Verification: analysis says OK correctness property
Load more

Recommended publications
  • IBM Developer for Z/OS Enterprise Edition
    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
    [Show full text]
  • Opportunities and Open Problems for Static and Dynamic Program Analysis Mark Harman∗, Peter O’Hearn∗ ∗Facebook London and University College London, UK
    1 From Start-ups to Scale-ups: Opportunities and Open Problems for Static and Dynamic Program Analysis Mark Harman∗, Peter O’Hearn∗ ∗Facebook London and University College London, UK Abstract—This paper1 describes some of the challenges and research questions that target the most productive intersection opportunities when deploying static and dynamic analysis at we have yet witnessed: that between exciting, intellectually scale, drawing on the authors’ experience with the Infer and challenging science, and real-world deployment impact. Sapienz Technologies at Facebook, each of which started life as a research-led start-up that was subsequently deployed at scale, Many industrialists have perhaps tended to regard it unlikely impacting billions of people worldwide. that much academic work will prove relevant to their most The paper identifies open problems that have yet to receive pressing industrial concerns. On the other hand, it is not significant attention from the scientific community, yet which uncommon for academic and scientific researchers to believe have potential for profound real world impact, formulating these that most of the problems faced by industrialists are either as research questions that, we believe, are ripe for exploration and that would make excellent topics for research projects. boring, tedious or scientifically uninteresting. This sociological phenomenon has led to a great deal of miscommunication between the academic and industrial sectors. I. INTRODUCTION We hope that we can make a small contribution by focusing on the intersection of challenging and interesting scientific How do we transition research on static and dynamic problems with pressing industrial deployment needs. Our aim analysis techniques from the testing and verification research is to move the debate beyond relatively unhelpful observations communities to industrial practice? Many have asked this we have typically encountered in, for example, conference question, and others related to it.
    [Show full text]
  • Building Useful Program Analysis Tools Using an Extensible Java Compiler
    Building Useful Program Analysis Tools Using an Extensible Java Compiler Edward Aftandilian, Raluca Sauciuc Siddharth Priya, Sundaresan Krishnan Google, Inc. Google, Inc. Mountain View, CA, USA Hyderabad, India feaftan, [email protected] fsiddharth, [email protected] Abstract—Large software companies need customized tools a specific task, but they fail for several reasons. First, ad- to manage their source code. These tools are often built in hoc program analysis tools are often brittle and break on an ad-hoc fashion, using brittle technologies such as regular uncommon-but-valid code patterns. Second, simple ad-hoc expressions and home-grown parsers. Changes in the language cause the tools to break. More importantly, these ad-hoc tools tools don’t provide sufficient information to perform many often do not support uncommon-but-valid code code patterns. non-trivial analyses, including refactorings. Type and symbol We report our experiences building source-code analysis information is especially useful, but amounts to writing a tools at Google on top of a third-party, open-source, extensible type-checker. Finally, more sophisticated program analysis compiler. We describe three tools in use on our Java codebase. tools are expensive to create and maintain, especially as the The first, Strict Java Dependencies, enforces our dependency target language evolves. policy in order to reduce JAR file sizes and testing load. The second, error-prone, adds new error checks to the compilation In this paper, we present our experience building special- process and automates repair of those errors at a whole- purpose tools on top of the the piece of software in our codebase scale.
    [Show full text]
  • The Art, Science, and Engineering of Fuzzing: a Survey
    1 The Art, Science, and Engineering of Fuzzing: A Survey Valentin J.M. Manes,` HyungSeok Han, Choongwoo Han, Sang Kil Cha, Manuel Egele, Edward J. Schwartz, and Maverick Woo Abstract—Among the many software vulnerability discovery techniques available today, fuzzing has remained highly popular due to its conceptual simplicity, its low barrier to deployment, and its vast amount of empirical evidence in discovering real-world software vulnerabilities. At a high level, fuzzing refers to a process of repeatedly running a program with generated inputs that may be syntactically or semantically malformed. While researchers and practitioners alike have invested a large and diverse effort towards improving fuzzing in recent years, this surge of work has also made it difficult to gain a comprehensive and coherent view of fuzzing. To help preserve and bring coherence to the vast literature of fuzzing, this paper presents a unified, general-purpose model of fuzzing together with a taxonomy of the current fuzzing literature. We methodically explore the design decisions at every stage of our model fuzzer by surveying the related literature and innovations in the art, science, and engineering that make modern-day fuzzers effective. Index Terms—software security, automated software testing, fuzzing. ✦ 1 INTRODUCTION Figure 1 on p. 5) and an increasing number of fuzzing Ever since its introduction in the early 1990s [152], fuzzing studies appear at major security conferences (e.g. [225], has remained one of the most widely-deployed techniques [52], [37], [176], [83], [239]). In addition, the blogosphere is to discover software security vulnerabilities. At a high level, filled with many success stories of fuzzing, some of which fuzzing refers to a process of repeatedly running a program also contain what we consider to be gems that warrant a with generated inputs that may be syntactically or seman- permanent place in the literature.
    [Show full text]
  • T-Fuzz: Fuzzing by Program Transformation
    T-Fuzz: Fuzzing by Program Transformation Hui Peng1, Yan Shoshitaishvili2, Mathias Payer1 Purdue University1, Arizona State University2 A PRESENTATION BY MD SHAMIM HUSSAIN AND NAFIS NEEHAL CSCI 6450 - PRINCIPLES OF PROGRAM ANALYSIS 1 Outline • Brief forecast • Background • Key Contributions • T-Fuzz Design • T-Fuzz Limitations • Experimental Results • Concluding Remarks • References CSCI 6450 - PRINCIPLES OF PROGRAM ANALYSIS 2 Fuzzing • Randomly generates input to discover bugs in the target program • Highly effective for discovering vulnerabilities • Standard technique in software development to improve reliability and security • Roughly two types of fuzzers - generational and mutational • Generational fuzzers require strict format for generating input • Mutational fuzzers create input by randomly mutating or by random seeds CSCI 6450 - PRINCIPLES OF PROGRAM ANALYSIS 3 Challenges in Fuzzing • Shallow coverage • “Deep Bugs” are hard to find • Reason – fuzzers get stuck at complex sanity checks Shallow Code Path Fig 1: Fuzzing limitations CSCI 6450 - PRINCIPLES OF PROGRAM ANALYSIS 4 Existing Approaches and Limitations • Existing approaches that focus on input generation ◦ AFL (Feedback based) ◦ Driller (Concolic execution based) ◦ VUzzer (Taint analysis based) ◦ etc. • Limitations ◦ Heavyweight analysis (taint analysis, concolic execution) ◦ Not scalable (concolic execution) ◦ Gets stuck on complex sanity checks (e.g. checksum values) ◦ Slow progress for multiple sanity checks (feedback based) CSCI 6450 - PRINCIPLES OF PROGRAM ANALYSIS
    [Show full text]
  • An Efficient Data-Dependence Profiler for Sequential and Parallel Programs
    An Efficient Data-Dependence Profiler for Sequential and Parallel Programs Zhen Li, Ali Jannesari, and Felix Wolf German Research School for Simulation Sciences, 52062 Aachen, Germany Technische Universitat¨ Darmstadt, 64289 Darmstadt, Germany fz.li, [email protected], [email protected] Abstract—Extracting data dependences from programs data dependences without executing the program. Although serves as the foundation of many program analysis and they are fast and even allow fully automatic parallelization transformation methods, including automatic parallelization, in some cases [13], [14], they lack the ability to track runtime scheduling, and performance tuning. To obtain data dependences, more and more related tools are adopting profil- dynamically allocated memory, pointers, and dynamically ing approaches because they can track dynamically allocated calculated array indices. This usually makes their assessment memory, pointers, and array indices. However, dependence pessimistic, limiting their practical applicability. In contrast, profiling suffers from high runtime and space overhead. To dynamic dependence profiling captures only those depen- lower the overhead, earlier dependence profiling techniques dences that actually occur at runtime. Although dependence exploit features of the specific program analyses they are designed for. As a result, every program analysis tool in need profiling is inherently input sensitive, the results are still of data-dependence information requires its own customized useful in many situations, which is why such profiling profiler. In this paper, we present an efficient and at the forms the basis of many program analysis tools [2], [5], same time generic data-dependence profiler that can be used [6]. Moreover, input sensitivity can be addressed by running as a uniform basis for different dependence-based program the target program with changing inputs and computing the analyses.
    [Show full text]
  • Static Program Analysis As a Fuzzing Aid
    Static Program Analysis as a Fuzzing Aid Bhargava Shastry1( ), Markus Leutner1, Tobias Fiebig1, Kashyap Thimmaraju1, Fabian Yamaguchi2, Konrad Rieck2, Stefan Schmid3, Jean-Pierre Seifert1, and Anja Feldmann1 1 TU Berlin, Berlin, Germany [email protected] 2 TU Braunschweig, Braunschweig, Germany 3 Aalborg University, Aalborg, Denmark Abstract. Fuzz testing is an effective and scalable technique to per- form software security assessments. Yet, contemporary fuzzers fall short of thoroughly testing applications with a high degree of control-flow di- versity, such as firewalls and network packet analyzers. In this paper, we demonstrate how static program analysis can guide fuzzing by aug- menting existing program models maintained by the fuzzer. Based on the insight that code patterns reflect the data format of inputs pro- cessed by a program, we automatically construct an input dictionary by statically analyzing program control and data flow. Our analysis is performed before fuzzing commences, and the input dictionary is sup- plied to an off-the-shelf fuzzer to influence input generation. Evaluations show that our technique not only increases test coverage by 10{15% over baseline fuzzers such as afl but also reduces the time required to expose vulnerabilities by up to an order of magnitude. As a case study, we have evaluated our approach on two classes of network applications: nDPI, a deep packet inspection library, and tcpdump, a network packet analyzer. Using our approach, we have uncovered 15 zero-day vulnerabilities in the evaluated software that were not found by stand-alone fuzzers. Our work not only provides a practical method to conduct security evalua- tions more effectively but also demonstrates that the synergy between program analysis and testing can be exploited for a better outcome.
    [Show full text]
  • 5 Key Considerations Towards the Adoption of a Mainframe Inclusive Devops Strategy
    5 Key Considerations Towards the Adoption of a Mainframe Inclusive DevOps Strategy Key considaetrations towards the adoption of a mainframe inclusive devops strategy PLANNING FOR DEVOPS IN MAINFRAME ENVIRONMENTS – KEY CONSIDERATIONS – A mountain of information is available around the implementation and practice of DevOps, collectively encompassing people, processes and technology. This ranges significantly from the implementation of tool chains to discussions around DevOps principles, devoid of technology. While technology itself does not guarantee a successful DevOps implementation, the right tools and solutions can help companies better enable a DevOps culture. Unfortunately, the majority of conversations regarding DevOps center around distributed environments, neglecting the platform that still runs more than 70% of the business and transaction systems in the world; the mainframe. It is estimated that 5 billion lines of new COBOL code are added to live systems every year. Furthermore, 55% of enterprise apps and an estimated 80% of mobile transactions touch the mainframe at some point. Like their distributed brethren, mainframe applications benefit from DevOps practices, boosting speed and lowering risk. Instead of continuing to silo mainframe and distributed development, it behooves practitioners to increase communication and coordination between these environments to help address the pressure of delivering release cycles at an accelerated pace, while improving product and service quality. And some vendors are doing just that. Today, vendors are increasing their focus as it relates to the modernization of the mainframe, to not only better navigate the unavoidable generation shift in mainframe staffing, but to also better bridge mainframe and distributed DevOps cultures. DevOps is a significant topic incorporating community and culture, application and infrastructure development, operations and orchestration, and many more supporting concepts.
    [Show full text]
  • Engineering Static Analysis Techniques for Industrial Applications
    Eighth IEEE International Working Conference on Source Code Analysis and Manipulation 90% Perspiration: Engineering Static Analysis Techniques for Industrial Applications Paul Anderson GrammaTech, Inc. 317 N. Aurora St. Ithaca, NY 14850 [email protected] Abstract gineered to allow it to operate on very large programs. Sec- tion 4 describes key decisions that were taken to expand This article describes some of the engineering ap- the reach of the tool beyond its original conception. Sec- proaches that were taken during the development of Gram- tion 5 discusses generalizations that were made to support maTech’s static-analysis technology that have taken it from multiple languages. Section 6 describes the compromises to a prototype system with poor performance and scalability principles that had to be made to be successful. Section 7 and with very limited applicability, to a much-more general- briefly describes anticipated improvements and new direc- purpose industrial-strength analysis infrastructure capable tions. Finally, Section 8 presents some conclusions. of operating on millions of lines of code. A wide variety of code bases are found in industry, and many extremes 2. CodeSurfer of usage exist, from code size through use of unusual, or non-standard features and dialects. Some of the problems associated with handling these code-bases are described, CodeSurfer is a whole-program static analysis infras- and the solutions that were used to address them, including tructure. Given the source code of a program, it analyzes some that were ultimately unsuccessful, are discussed. the program and produces a set of representations, on which static analysis applications can operate.
    [Show full text]
  • Program Analysis Via Graph Reachability
    Program Analysis Mooly Sagiv http://www.cs.tau.ac.il/~msagiv/courses/pa 16.html Formalities • Prerequisites: Compilers or Programming Languages • Course Grade – 10 % Lecture Summary (latex+examples within one week) – 45% 4 assignments – 45% Final Course Project (Ivy) Motivation • Compiler optimizations – Common subexpressions – Parallelization • Software engineering • Security Class Notes • Prepare a document with latex – Original material covered in class – Explanations – Questions and answers – Extra examples – Self contained • Send class notes by Monday morning to msagiv@tau • Incorporate changes • Available next class • A sailor on the U.S.S. Yorktown entered a 0 into a data field in a kitchen-inventory program • The 0-input caused an overflow, which crashed all LAN consoles and miniature remote terminal units • The Yorktown was dead in the water for about two hours and 45 minutes Numeric static analysis can detect these errors when the ship is built! • A sailor on the U.S.S. Yorktown entered a 0 into a data field in a kitchen-inventory program • The 0-input caused an overflow, which crashed all LAN consoles and miniature remote terminal units • The Yorktown was dead in the water for about two hours and 45 minutes x = 3; need to track values y = 1/(x-3); other than 0 x = 3; need to track px = &x; pointers y = 1/(*px-3); for (x =5; x < y ; x++) { Need to reason y = 1/ z - x about loops Dynamic Allocation (Heap) x = 3; need to track p = (int*)malloc(sizeof int); heap-allocated *p = x; storage q = p; y = 1/(*q-3); Why is Program Analysis
    [Show full text]
  • Web Environment for Program Analysis and Transformation Onto Reconfigurable Architectures
    Web Environment for Program Analysis and Transformation onto Reconfigurable Architectures A.P. Bagly[0000-0001-9089-4164] Southern Federal University, Rostov-on-Don 344006, Russia [email protected] Abstract. Experience of designing different versions of web-based development environment (IDE) for Optimizing parallelizing system and compiler onto reconfigurable architecture is described. Designed system is based on existing tools and frameworks such as Jupyter Note- book and Eclipse Che. Set of requirements for Optimizing parallelizing system components is developed to make it possible to integrate them into web-based development environment accessible through the Internet. Designing portable environment for compiler development, compiler technology demonstration and teaching parallel program development is also de- scribed. Newly developed program transformations are shown to be used during program opti- mizations for FPGA inside the designed web environment. Means of program transformation visualization are described for use with Jupyter Notebook. The work shown demonstrates pos- sibility to organize remote access to library of instruments and tools for program optimizations currently under development that would be convenient for application developers. Keywords: Integrated Development Environment, Program Transformations, Parallelizing Compiler, Containerization, Wed IDE, Cloud Computing, FPGA. 1 Introduction During development of a complex software system, like an optimizing compiler as an example, multitude of problems arise that concern overall organization of develop- ment process, deployment and usage of developed system. Complexities arise as well with regards to training and inclusion of new developers, organizing outside access to experimental results, like performing demonstrations of particular functions. Problems that arise are in many ways similar to those that are faced by program- mers not familiar with software development for field-programmable gate arrays, as it requires using complex development environments.
    [Show full text]
  • Static Program Analysis for Performance Modeling
    Static Program Analysis for Performance Modeling Kewen Meng, Boyana Norris Department of Computer and Information Science University of Oregon Eugene, Oregon fkewen, [email protected] Abstract—The performance model of an application potential optimization opportunities. can provide understanding about its runtime behavior on As the development of new hardware and archi- particular hardware. Such information can be analyzed tectures progresses, the computing capability of high by developers for performance tuning. However, model performance computing (HPC) systems continues to building and analyzing is frequently ignored during increase dramatically. However along with the rise software development until performance problems arise because they require significant expertise and can involve in computing capability, it is also true that many many time-consuming application runs. In this paper, applications cannot use the full available computing we propose a faster, accurate, flexible and user-friendly potential, which wastes a considerable amount of com- tool, Mira, for generating intuitive performance models puting power. The inability to fully utilize available by applying static program analysis, targeting scientific computing resources or specific advantages of architec- applications running on supercomputers. Our tool parses tures during application development partially accounts both the source and binary to estimate performance for this waste. Hence, it is important to be able to attributes with better accuracy than considering just understand and model program behavior in order to source or just binary code. Because our analysis is gain more information about its bottlenecks and per- static, the target program does not need to be exe- cuted on the target architecture, which enables users to formance potential.
    [Show full text]