{"id":23670,"date":"2022-12-15T11:07:17","date_gmt":"2022-12-15T11:07:17","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/15\/rust-support-merged-for-the-forthcoming-gcc-13-the-register\/"},"modified":"2022-12-15T11:07:17","modified_gmt":"2022-12-15T11:07:17","slug":"rust-support-merged-for-the-forthcoming-gcc-13-the-register","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/15\/rust-support-merged-for-the-forthcoming-gcc-13-the-register\/","title":{"rendered":"Rust support merged for the forthcoming GCC 13 \u2022 The Register"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Preliminary support for compiling the Rust language has been merged into the codebase for GCC 13, which will be the next version of the GNU compiler collection.<\/p>\n

The Reg<\/em>‘s sister site DevClass reported on the approval<\/a> back in July, along with a timeline of when to expect the next steps, and now the code merge has happened. This is a good thing, and it’s significant step for the Rust language \u2013 but there is a whole list of “buts” attached to this news.<\/p>\n

The Rust-GCC<\/a> project has been underway for a couple of years, as can be seen from the earliest commits on its Github<\/a> page. The last time we wrote about it, when covering Linus Torvalds’ keynote at the Open Source Summit<\/a>, we attracted criticism for, um, quoting the project’s own description from that page, saying how preliminary it was. Some Rustaceans regarded this as unfair, which may possibly tell you more about the fervor of Rust fans than it tells you about the GCC compiler’s state of completion.<\/p>\n

\n