## +24 ## Security Beyond Memory Safety Using Modern C++ to Avoid Vulnerabilities by Design ## MAX HOFFMANN ## Security Beyond Memory Safety Using Modern C++ to Avoid Vulnerabilities by Design FIFTY today's C++. ## Carbon Language: An experimental successor to C++ ## Memory safety Safety, and especially memory safety, remains a key challenge for C++ and something a successor language needs to address Our initial priority and focus is on immediately addressing important, low-hanging fruit in the safety space: ## New Circle is out! • New Circle notes New Circle is a major transformation of the Circle

## +24 ## Improving Our Safety With a Quantities and Units Library ## MATEUSZ PUSZ ## The future is here  ## The future Computer  ## C++ safety • A major concern in the C++ Community in the recent years • Potential improvements are being discussed library ## • Compile-time safety – correct handling of physical quantities, units, and numerical values ## mp-units: C++20/23 quantities and units library ## • Compile-time safety – correct handling of

## +21 ## Misra Parallelism Safety-critical Guidelines for C++11, 17, Then C++20, 23 ANDREAS WEIS, MICHAEL WONG & ILYA BURYLOV 20 21 October 24-29 ## Staff Engineer at Woven Planet 📸 / 🎧 ComicSansMS architect of C++ software solutions for autonomous driving market in Intel Contribution into functional safety MISRA standard Contribution into WG21 in threading, vectorization and numerics. Contribution into can't have them. ## Agenda 1. Current status of C++ safety: MISRA and C++ CG 2. Parallel Safety rules 3. Automotive Safety case ## Safety Critical API Evolution ![Image](/uploads/documents/8/d/

## 20 23 October 01 - 06 ## +23 ## Lifetime Safety in C++: Past, Present and Future #### GABOR HORVATH Gabor.Horvath@microsoft.com ## Welcome to CppCon 2023! Come by our booth and join #visual_studio ecbd0a2aac297caf075ed3c2/p4_1.jpg) Approaches to safety ## ↑ C++ is getting safer The lifetime safety toolbox What comes next? 2023 ## Safety & Security: The Future of C++ JF Bastien  All the Sean Parer Coding for Safety, Security, and

## Khronos APIs for Heterogeneous Compute and Safety: SYCL and SYCL SC MICHAEL WONG, NEVIN LIBER & VERENA BECKHAM ## Open Standards and Open Source implementations, community driven Open cross-company [Image](/uploads/documents/f/e/2/6/fe26ba058e18c308786b2683cbd327df/p23_1.jpg) ## 3 Pre-exasacale ## KHRONOS SAFETY CRITICAL STANDARDS EVOLUTION  OpenGL SC 1.0 - 2005 Fixed function graphics safety-critical subset 

## +24 ## LLVM's Realtime Safety Revolution: Tools for Modern Mission Critical Systems DAVID TREVELYAN & CHRISTOPHER APPLE ## Chris Apple ## David Trevelyan • 10-year veteran of the audio industry dependencies? ## What if we had a tool that could simply tell us? ## A nice tool would - Assess real-time safety - Detect a wide range of violations - ...even from third-party and pre-compiled dependencies - - Point to any problematic code - Be able to fail a Cl pipeline build unit tests real-time safety build:mac unit:mac rtsan build:win unit:mac:arm build:linux unit:win unit:linux ## LLVM 20

☐☐☐☐ FFI - . . . . .LSP ☐☐☐☐☐☐☐☐☐☐☐☐☐☐☐☐☐ - . ☐☐ C ☐☐ ++C (borrow □□ ++C ☐☐ ( memory safety) ☐ ++C ( ### Playground 4.3 ☐ ☐ ☐ ☐ □ playground ☐☐☐☐ ## 5 ☐☐☐ ## ☐☐☐☐☐☐ ☐ ☐☐☐☐☐☐ :□□□□□□ ☐☐☐☐ ☐☐☐☐ ☐☐☐☐☐☐☐ 30.3 :□□□ □ ;static mut COUNTER: u32 = 0 } (fn add_to_counter(inc: u32 . 'SAFETY: There are no other threads which could be accessing 'COUNTER // } unsafe ;COUNTER += inc "C" ; fn abs(input: i32) -> i32 } { "main" "= let emojis" } SAFETY: The indices are in the correct order, within the bounds of the // .string slice, and lie on UTF-8

compilation - distributed systems - multicore, networked hardware And a reaction to: “speed and safety or ease of use; pick one.” - complexity, weight, noise (C++, Java) vs. - no static checking (JavaScript

① Why Safety/Security in C++ ② Medical Device Failure Analysis ③ Brief Intro to Medical Device Standards, Documents, and Reports ④ Safety in C++ and What We Can Do ⑤ Coding Practices in Safety Critical Critical Path ⑥ Final Words and Q&A ## Safety/Security and C++ ## Security/Safety Concerns with C++ Software Memory Safety  NATIONAL COORDINATOR FOR CRITICAL INFRASTRUCTURE SECURITY AND RESILIENCE The Urgent Need for Memory Safety in Software Products Released: September 20, 2023 Revised: December 06, 2023 The Case for Memory

2 cppfront: Recap Safety for C++ 50 esp. guaranteed program-meaningful initialization Simplicity for C++ 10 esp. for programmers cppfront: What’s new Types, reflection, metafunctions, … Simplification demarcated “bubble of new code,” via an alternate syntax for C++? reduce complexity 10 increase safety 50 improve toolability 10 evolve more freely for another 30 years syntax… #2 ? “bubble of new Ezekiel Warren, Kayla Washburn, Tyler Weaver, Will Wray 8 Safety (goal: 50 fewer CVEs due to type, bounds, lifetime, and init safety) Bounds and null checking by default, incl. when using existing