Quality Assurance and Coding Standards for Parallel Software on POWER systems
summary
Describes an effort to define QA practices and coding standards for parallel programming on POWER systems, collecting expert best practices and targeting industry and novice HPC programmers. Covers development of new static code-analysis tools specialized for detecting parallelism-related issues and enforcing those standards on POWER (OpenPOWER) platforms.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:02Outline
- 2:05Coding Standards for...
- 4:15Example: SEI CERT C Coding Standard for Cybersecurity Coding standards for quality
- 4:48What about Coding Standards for Parallelism?
- 5:59About Appentra and Parallelwar
- 6:55Definition of Parallel Software
- 8:24Use cases of Parallel Software
- 8:58The Core of Parallel Software Development
- 9:50Beyond the Core of Parallel Software Developer
- 10:35EPEEC Guidelines (First released in June 2020)
- 11:27Parallelware Analyzer Capabilities to help developing parallel software
- 12:25Value proposition - Parallelware Analyzer 0.15
- 12:42Command-line tools for each stage of the parallelization process
- 14:07List of defects/recommendations with pwloop
- 14:39List of defects/recommendations with pwdirect
- 15:04What is Specific for OpenPOWER? • POWER is a perfect match for supercomputing
related talks
01h 19mCo-Design for High-Performance Computing Software Systems
20mRevolution in IT
01h 02mA Critical Look at the Coding Standards Landscape
25mBest Practices for Writing Clean and Maintainable Codes
12mCode of conduct developing medical grade software
27mContinuous Compliance: Agile Practices for Software Compliance
30mDesign Patterns for Handling/Reporting Errors in C++ - Parallel Algorithms & Executors
21mSoftware for Quantum Computing- Easing Solutions for Complex