{"id":651922,"date":"2025-12-24T06:00:34","date_gmt":"2025-12-24T06:00:34","guid":{"rendered":"https:\/\/www.europesays.com\/uk\/651922\/"},"modified":"2025-12-24T06:00:34","modified_gmt":"2025-12-24T06:00:34","slug":"llvm-considering-an-ai-tool-policy-ai-bot-for-fixing-build-system-breakage-proposed","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/uk\/651922\/","title":{"rendered":"LLVM Considering An AI Tool Policy, AI Bot For Fixing Build System Breakage Proposed"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" alt=\"LLVM\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/12\/llvm.webp.webp\" width=\"100\" height=\"100\"\/><br \/>\nLast week a request for comments (RFC) was issued around establishing an LLVM AI Tool Use Policy. The proposed policy would allow AI-assisted contributions to be made to this open-source compiler codebase but that there would need to be a &#8220;human in the loop&#8221; and the contributor versed enough to be able to answer questions during code review. Separately, yesterday a proposal was sent out for creating an AI-assisted fixer bot to help with Bazel build system breakage.<\/p>\n<p>Last week&#8217;s <a href=\"https:\/\/discourse.llvm.org\/t\/rfc-llvm-ai-tool-policy-human-in-the-loop\/89159\" target=\"_blank\" rel=\"noopener\">LLVM AI tool policy<\/a> was brought up for discussion. AI-assisted contributions would be welcome as long as there is a human in the loop that understands the code and competent enough for answering any questions during the code review. Contributors should also be transparent if there are &#8220;substantial amounts&#8221; of tool-generated content. <a href=\"https:\/\/github.com\/llvm\/llvm-project\/pull\/154441\" target=\"_blank\" rel=\"noopener\">This pull request<\/a> in turn is open on GitHub for adding their AI contribution policy to the LLVM documentation. That LLVM Ai tool policy remains under discussion.&#13;<br \/>\n<\/p>\n<p align=\"center\"><img decoding=\"async\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/12\/1766556034_65_image\" alt=\"LLVM AI fun\"\/><\/p>\n<p>Separately, raised yesterday for request for comments was a <a href=\"https:\/\/discourse.llvm.org\/t\/rfc-ai-assisted-bazel-fixer-bot\/89178\" target=\"_blank\" rel=\"noopener\">proposal<\/a> by Google compiler engineer Pranav Kant for creating an AI-assisted Bazel fixer bot. This AI bot would automatically create AI-generated pull requests for fixing broken LLVM builds when using the Bazel build system. Google is a big user of the Bazel build system but LLVM contributors are not required to update their changes around Bazel builds. Thus Google compiler engineers would like an experimental AI-assisted bot for helping to maintain their Bazel build support in LLVM.<\/p>\n<p>The original proposal there calls for this AI bot to create the pull requests with fixes, but some have taken some objection to that part. Some would prefer a human to at least evaluate the proposed changes first rather than the bot creating the PRs straight-away and creating a bigger burden on LLVM developers to review that code straight from a bot.&#13;\n<\/p>\n<p>Meanwhile GNU toolchain developers have also been <a href=\"https:\/\/www.phoronix.com\/news\/GCC-To-Consider-LLM-Patches\" target=\"_blank\" rel=\"noopener\">considering an AI\/LLM policy for the GCC compiler<\/a> too.<\/p>\n","protected":false},"excerpt":{"rendered":"Last week a request for comments (RFC) was issued around establishing an LLVM AI Tool Use Policy. The&hellip;\n","protected":false},"author":2,"featured_media":651923,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3163],"tags":[323,1942,2228,2227,2225,2224,2231,2229,2226,2230,2223,2234,53,2232,2233,16,15],"class_list":{"0":"post-651922","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-artificial-intelligence","8":"tag-ai","9":"tag-artificial-intelligence","10":"tag-desktop-linux","11":"tag-linux-benchmarking","12":"tag-linux-hardware-benchmarks","13":"tag-linux-hardware-reviews","14":"tag-linux-how-to","15":"tag-linux-performance","16":"tag-linux-server-benchmarks","17":"tag-open-source-graphics","18":"tag-phoronix","19":"tag-phoronix-test-suite","20":"tag-technology","21":"tag-ubuntu-benchmarks","22":"tag-ubuntu-hardware","23":"tag-uk","24":"tag-united-kingdom"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@uk\/115773022854023015","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/651922","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/comments?post=651922"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/651922\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media\/651923"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media?parent=651922"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/categories?post=651922"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/tags?post=651922"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}