GCC Adopts Policy Rejecting Significant AI-Generated Code

The GNU Compiler Collection will reject copyright-significant contributions derived from LLM output, with limited exceptions for trivial changes and test cases.

The GCC Steering Committee has officially adopted a new policy governing the use of artificial intelligence and large language models in contributions to the GNU Compiler Collection.

According to the new rules, the GCC will, for the time being, turn down any contributions that include material protected by copyright and produced by an LLM or based on output generated by such a system.

This covers not just code copied directly from tools like ChatGPT, Gemini, or GitHub Copilot, but also any versions of the code later edited or rewritten by a human, provided that the final contribution is still based on material generated by the system.

The important point, then, is not whether a developer has used an AI tool at some stage in their work; contributors can use LLMs to discuss ideas, understand existing code, learn about a field they are unfamiliar with, or carry out general research. The limitation lies in the inclusion of copyright-significant material generated by such tools in the code submitted to GCC.

The policy also provides for a few limited exceptions; GCC maintainers are allowed to accept changes that are legally insignificant or trivial and are generated by an LLM, on the condition that they meet the project’s normal contribution requirements and the use of an LLM is clearly disclosed.

Furthermore, copyright-significant AI-generated test cases could still be accepted. Since test cases usually involve small programs which are intended to reproduce compiler bugs or to verify certain behavior, the policy deals with them separately from code that is incorporated into GCC itself.

It does not follow that merely looking at or altering the generated code makes it acceptable. By the rules that have been adopted, a contributor cannot take substantial implementation produced by an LLM, clean it up manually, and then treat the resulting patch as if it had been originally written by them.

Once a contribution has been derived from generated content, it is still subject to the policy. For additional details, see here.

Bobby Borisov

Bobby Borisov

Bobby, an editor-in-chief at Linuxiac, is a Linux professional with over 20 years of experience. With a strong focus on Linux and open-source software, he has worked as a Senior Linux System Administrator, Software Developer, and DevOps Engineer for small and large multinational companies.

Leave a Reply

Your email address will not be published. Required fields are marked *