{"id":103436,"date":"2022-02-25T21:37:00","date_gmt":"2022-02-25T19:37:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-yadre-linux-5-18-planiruyut-razreshit-ispolzovanie-standarta-yazyka-si-c11"},"modified":"2022-02-25T21:37:00","modified_gmt":"2022-02-25T19:37:00","slug":"v-yadre-linux-5-18-planiruyut-razreshit-ispolzovanie-standarta-yazyka-si-c11","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-yadre-linux-5-18-planiruyut-razreshit-ispolzovanie-standarta-yazyka-si-c11","title":{"rendered":"In the Linux 5.18 kernel, the use of the C11 standard is planned to be permitted.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
During the discussion of the patch set addressing issues related to vulnerabilities of the Spectre class in the code for handling linked lists, it became clear that the problem could be resolved more elegantly if the kernel allowed C code conformed to a newer version of the standard. Currently, the code added to the kernel must comply with the ANSI C (C89) specification, which was established back in 1989. <\/p>\n
The issue related to Spectre in the code was caused by the continued use of a separately defined iterator after the loop \u2014 a macro is used to iterate over the elements of a linked list, and since the loop iterator is passed into this macro, it is defined outside of the loop itself and remains accessible after the loop. Using the C99 standard would have allowed defining loop variables in the for() block, which would have solved the problem without resorting to workarounds. <\/p>\n
Linus Torvalds agreed with the idea of implementing support for newer specifications and proposed transitioning in kernel 5.18 to use the C11 standard, published in 2011. Preliminary checks showed that the build in GCC and Clang in the new mode went smoothly. If no unforeseen issues arise during more thorough testing, in the build scripts for kernel 5.18 the option \u2018--std=gnu89\u2019 will be replaced with \u2018--std=gnu11 -Wno-shift-negative-value\u2019. The possibility of using the C17 standard was also considered, but in that case, the minimum supported version of GCC would have to be raised. However, including support for C11 fits within the current requirements for GCC (5.1). \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"