当前位置:首页 > 报告详情

John_C++ “安全优先”开发模式演进与路线图.pdf

上传人: 柒柒 编号:1268173 2026-06-13 78页 5.57MB

1、 2025 Bloomberg Finance L.P.All rights reserved.What C+Needs to be Safe?C+C+需要些什么才能安全?需要些什么才能安全?C+Summit25December 12-13,2025Modified Monday,Dec 1st,2025John LakosSenior Architect,Office of the CTO 首席技术官办公室高级架构师What C+Needs to be Safe?John LakosBloomberg,CTORevised December 1,20257AbstractThe world

2、runs on C+.For more than two decades,C+has served as the workhorse of high-performance,low-power,and low-latency software across industries.Its raw speed and unconstrained flexibility have made C+the go-to language for and backbone of large-scale software development.C+是驱动世界运转的核心语言。二十多年来,它始终是各行业高性能、

3、低功耗、低延迟软件的主力担当。凭借其极致速度与无拘无束的灵活性,C+已成为大规模软件开发的首选语言和核心支柱。Recently,however,software engineering priorities have shifted significantly toward safety.While C+enables the creation of secure and correct programs,its traditional focus has favored performance over safety guarantees.As the software landscape

4、evolves,C+faces a crucial inflection point.To maintain its unparalleled stature,C+must embrace various safety mechanisms along with safety-by-default principles to support a broader developer ecosystem while preserving the performance capabilities that experts will continue to demand.然而近年来,软件工程的重心已显

5、著向安全性倾斜。尽管 C+语言能够开发出安全可靠的程序,但其传统定位始终更侧重性能而非安全保障。随着软件生态的持续演进,C+正面临关键转折点。为保持其无可替代的地位,C+必须拥抱多种安全机制与默认安全原则,既要维护开发者生态系统的广泛性,又要确保满足技术专家持续追求的性能表现。This talk will examine C+s evolution toward safety-first development,analyzing functional,language,memory,lifetime,and data-race safety considerations.We survey

6、existing safety techniques,identify current limitations,and explore potential solutions for remaining security challenges.Finally,we present a comprehensive roadmap for achieving robust safety guarantees in C+26 and beyond,while continuing to enable all the languages performance advantages.本次演讲将深入探讨

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
1. **C++安全转型必要性**:C++因性能优先面临安全批评(谷歌、微软等企业转向Rust),需通过安全机制(如契约、内存安全)保持竞争力。 2. **核心安全目标**: - **安全性**:消除核心语言未定义行为(UB),无需修改代码即可构建无UB程序。 - **正确性**:支持运行时契约检查(前置/后置条件),如`std::vector`边界检查可防范65% STL漏洞。 3. **关键技术路径**: - **C++26契约MVP**:支持`pre/post`条件、四种违反语义(ignore/enforce等)。 - **错误行为(EB)**:定义未初始化读取等为错误,防止安全漏洞。 - **编译期独占性**:如Swift风格迭代中禁止可变引用。 4. **优先级**:65%漏洞源于数组越界,20%为契约违反,需重点解决。
C++安全之路 契约如何保障安全? 内存安全新方案
客服
商务合作
小程序
服务号
折叠