--- title: GCC Compiler Bans AI Code Contribution But Sensibly description: The GCC Steering Committee has adopted a new AI policy that bans legally significant contributions (roughly 15+ lines of code) generated with AI tools. Legally... canonical: https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GCC Compiler Bans AI Code Contribution But Sensibly | daily.dev og:description: The GCC Steering Committee has adopted a new AI policy that bans legally significant contributions (roughly 15+ lines of code) generated with AI tools. Legally... og:url: https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru og:image: https://api.daily.dev/og/posts/VsQFr5IRU.png og:image:alt: GCC Compiler Bans AI Code Contribution But Sensibly og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # GCC Compiler Bans AI Code Contribution But Sensibly **[It's Foss](https://daily.dev/sources/itsfoss)** · 3 min read · 5 upvotes · 1 comments ## Summary The GCC Steering Committee has adopted a new AI policy that bans legally significant contributions (roughly 15+ lines of code) generated with AI tools. Legally insignificant AI contributions are still allowed if clearly marked with an 'Assisted-by:' tag, and AI-generated test cases are fully exempted. The policy does not restrict how contributors use AI privately for research, bug hunting, or review. A review is planned for early 2027. This positions GCC closer to Codeberg's stricter stance than LLVM's permissive 'human in the loop' approach, reflecting a broader split in open source communities over AI-generated contributions. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is GCC's new policy on AI-generated code contributions? GCC now declines contributions that are 'legally significant' if any part traces back to an LLM, following the GNU maintainer guideline threshold of roughly 15 lines of code or text where copyright applies. Smaller AI-generated edits are allowed if clearly marked, and AI-generated test cases are exempt even if legally significant. All AI-assisted contributions require an 'Assisted-by:' tag in the commit message. The policy is set for review at the start of 2027. _Contributors adjusting workflows around AI use in open source can follow policy shifts like this on daily.dev._ ### How does GCC's AI contribution policy compare to Codeberg's and LLVM's? GCC's policy sits between Codeberg's outright ban and LLVM's permissive approach. Codeberg banned projects built mostly from AI-generated code after a 358-to-144 member vote, citing server strain and low-effort contributions. LLVM adopted a 'human in the loop' policy requiring disclosure of AI tools used but allowing any tool as long as the contributor takes full responsibility. GCC allows small, clearly marked AI contributions and AI-generated test cases, which Codeberg's rules don't permit. _Developers deciding how their project should handle AI contributions can compare these approaches on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@coppnic** · 4 upvotes > That's more of a clean and open approach than the Codeberg anti-AI stance. The GCC Discussion was mostly fair and well balanced, while in the discussions on Codeberg it was clear from the chosen taxonomy that it was purely ideologically anti-AI in its core. > > Elsewise, good article, good choice. This is basically the definition of human in the loop. What I don't get is, if I write 100% the same line as an AI would, what makes the difference? There is none, besides ideological bias. ## Similar posts on daily.dev - [GCC, the core compiler behind Linux, draws a hard line against AI code](https://daily.dev/posts/gcc-the-core-compiler-behind-linux-draws-a-hard-line-against-ai-code-wvhpm7hb7) · XDA Developers · 5 upvotes · 3 comments - [GCC steering committee announces AI policy](https://daily.dev/posts/gcc-steering-committee-announces-ai-policy-h9jt2hq9y) · LWN.net · 0 upvotes · 0 comments - [GCC To Decline Any Significant Contributions Made Via AI/LLMs - Except For Test Cases](https://daily.dev/posts/gcc-to-decline-any-significant-contributions-made-via-ai-llms---except-for-test-cases-63nu7mi9e) · Phoronix · 0 upvotes · 0 comments - [GCC Developers Considering Whether To Accept AI/LLM-Generated Patches](https://daily.dev/posts/gcc-developers-considering-whether-to-accept-ai-llm-generated-patches-lzzxzeesf) · Phoronix · 0 upvotes · 0 comments - [AI Can No Longer Rampage Through Rust's Code Repo](https://daily.dev/posts/ai-can-no-longer-rampage-through-rust-s-code-repo-npr4hm4wd) · It's Foss · 11 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#llm](https://daily.dev/tags/llm), [#ai-coding](https://daily.dev/tags/ai-coding) [View this post on daily.dev](https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"GCC Compiler Bans AI Code Contribution But Sensibly","url":"https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru"},"datePublished":"2026-07-30T10:10:31.120Z","dateModified":"2026-09-14T06:53:24.554Z","description":"The GCC Steering Committee has adopted a new AI policy that bans legally significant contributions (roughly 15+ lines of code) generated with AI tools. Legally...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a4d3f0f3b7352c0bb08ef3adcf644e20?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a4d3f0f3b7352c0bb08ef3adcf644e20?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"It's Foss","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"It's Foss","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/582e3faed71842bfb9d3840a787d6700","url":"https://daily.dev/sources/itsfoss"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"open-source,llm,ai-coding","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"It's Foss","item":"https://daily.dev/sources/itsfoss"},{"@type":"ListItem","position":3,"name":"GCC Compiler Bans AI Code Contribution But Sensibly"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru","comment":[{"@type":"Comment","text":"That’s more of a clean and open approach than the Codeberg anti-AI stance. The GCC Discussion was mostly fair and well balanced, while in the discussions on Codeberg it was clear from the chosen taxonomy that it was purely ideologically anti-AI in its core.\nElsewise, good article, good choice. This is basically the definition of human in the loop. What I don’t get is, if I write 100% the same line as an AI would, what makes the difference? There is none, besides ideological bias.","datePublished":"2026-07-30T11:14:37.355Z","url":"https://daily.dev/posts/VsQFr5IRU#c-DpPfcmAGQ","author":{"@type":"Person","name":"coppnic","url":"https://daily.dev/coppnic","image":"https://media.daily.dev/image/upload/s--8VyNl1cb--/f_auto/v1732889303/avatars/avatar_z5bNZJIOpNguomDjmmrE2"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/gcc-compiler-bans-ai-code-contribution-but-sensibly-vsqfr5iru#faq","mainEntity":[{"@type":"Question","name":"What is GCC's new policy on AI-generated code contributions?","acceptedAnswer":{"@type":"Answer","text":"GCC now declines contributions that are 'legally significant' if any part traces back to an LLM, following the GNU maintainer guideline threshold of roughly 15 lines of code or text where copyright applies. Smaller AI-generated edits are allowed if clearly marked, and AI-generated test cases are exempt even if legally significant. All AI-assisted contributions require an 'Assisted-by:' tag in the commit message. The policy is set for review at the start of 2027. Contributors adjusting workflows around AI use in open source can follow policy shifts like this on daily.dev."}},{"@type":"Question","name":"How does GCC's AI contribution policy compare to Codeberg's and LLVM's?","acceptedAnswer":{"@type":"Answer","text":"GCC's policy sits between Codeberg's outright ban and LLVM's permissive approach. Codeberg banned projects built mostly from AI-generated code after a 358-to-144 member vote, citing server strain and low-effort contributions. LLVM adopted a 'human in the loop' policy requiring disclosure of AI tools used but allowing any tool as long as the contributor takes full responsibility. GCC allows small, clearly marked AI contributions and AI-generated test cases, which Codeberg's rules don't permit. Developers deciding how their project should handle AI contributions can compare these approaches on daily.dev."}}]} ```