{"id":105257,"date":"2022-10-06T15:36:38","date_gmt":"2022-10-06T13:36:38","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/proekt-llvm-razvivaet-sredstva-dlya-bezopasnoj-raboty-s-buferami-v-c"},"modified":"2022-10-06T15:36:38","modified_gmt":"2022-10-06T13:36:38","slug":"proekt-llvm-razvivaet-sredstva-dlya-bezopasnoj-raboty-s-buferami-v-c","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/proekt-llvm-razvivaet-sredstva-dlya-bezopasnoj-raboty-s-buferami-v-c","title":{"rendered":"The LLVM project is developing tools for safe buffer handling in C++","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The developers of the LLVM project have proposed a number of changes aimed at enhancing the security of critical projects in C++ and providing tools to eliminate errors caused by buffer overflows. The work focuses on two main areas: providing a development model that allows for safe buffer handling, and enhancing the protection of the standard libc++ library. <\/p>\n
The proposed safe programming model for C++ emphasizes using the classes provided by the standard library when working with buffers instead of manipulating raw pointers. For example, it is suggested to use the std::array, std::vector, and std::span classes, which will include runtime checks for memory bounds violations. <\/p>\n
To combat dangerous programming practices in clang, it is proposed to emit compiler warnings for all arithmetic operations with pointers, similar to the warnings from clang-tidy's linter when using the flag 'cppcoreguidelines-pro-bounds-pointer-arithmetic,' which will be supported in the LLVM 16 release. A separate flag will be added to clang for enabling such warnings, which will be inactive by default. <\/p>\n
In libc++, there are plans to implement an optional enhanced protection mode, which, when enabled, will catch certain situations at runtime that lead to undefined behavior. For instance, in the std::span and std::vector classes, accesses beyond the allocated memory will be monitored, and if detected, the program will terminate abnormally. The developers believe that these changes will keep libc++ aligned with C++ standards, as the method of handling undefined behavior cases is up to library developers, who may interpret undefined behavior as failures necessitating program termination. <\/p>\n
During the runtime checks in libc++, categories are being planned for separation, which can be individually enabled. Some of the proposed checks that do not complicate operations or change the ABI are already implemented in safe mode libc++. <\/p>\n
Additionally, there are plans to prepare a toolset for code correction that allows replacing variables with raw pointers with containers and applying alternative handlers in situations where a container cannot directly replace a pointer (for example, the construct 'if(array_pointer)' could be transformed into 'if(span.data()). Corrections can be applied not only to local variables but also to type parameters with pointers. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"