{"id":35694,"date":"2019-10-31T22:05:48","date_gmt":"2019-10-31T19:05:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/razrabotchiki-iz-google-predlozhili-razrabotat-svoyu-libc-dlya-llvm\/"},"modified":"2019-10-31T22:05:48","modified_gmt":"2019-10-31T19:05:48","slug":"razrabotchiki-iz-google-predlozhili-razrabotat-svoyu-libc-dlya-llvm","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/razrabotchiki-iz-google-predlozhili-razrabotat-svoyu-libc-dlya-llvm","title":{"rendered":"Google developers proposed to create their own libc for LLVM","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

One of the developers from Google raised<\/a><\/noindex> the topic of developing a cross-platform standard C library (Libc) within the LLVM project on the LLVM mailing list. For various reasons, Google is not satisfied with the current libc (glibc, musl), and the company is on its way to developing a new implementation that is proposed to be evolved as part of LLVM.<\/p>\n

LLVM's developments have recently been used as a foundation for building Google's tooling. The main idea is that if Google has already started developing its own libc, then why not develop its system within LLVM, which already offers its standard library for C++ (Libc++), but lacks a similar standard library for C (Libc).<\/p>\n

The development is planned to be conducted in phases, gradually increasing functionality. The initial versions are proposed to be designed as a layer between the application and the system's Libc, from which still unimplemented features will be borrowed. After reaching a certain level of functionality, the new Libc will be able to be used as a complete replacement for the system's Libc. It will start with support for the x86-64 architecture, Linux, and static linking (dynamic loading, linking, and additional architectures will be implemented second). <\/p>\n

The project is still in its early stages, but basic goals have already been defined:<\/p>\n