GCC steering committee announces AI policy

In one line

The GCC steering committee has announced that it has accepted an AI contributions policy recomm […]

Opening excerpt

The policy, in part, states that the project will decline any ” legally significant contributions which include LLM-generated content or are derived from LLM-generated content ”. It uses the definition of “legally significant” from the GNU Project maintainer guidelines, which holds that the threshold is ” around 15 lines of code and/or text ” to qualify as significant for copyright purposes. GCC maintainers may, however, choose to accept legally significant test cases that are generated by an LLM.

The policy does not forbid use of LLMs for research, analysis, bug discovery and reporting, patch review, etc. as long as the output is not included in contributions. The committee says that it expects the policy will evolve and will be revisited periodically.

That’s a naive and outdated view of how these tools work. With models at the level of Opus 4.8 or GPT 5.5 and newer in the hand of a competent programmer the result is simply indistinguishable.

So given you don’t have such first-hand experience, don’t you feel a bit weird telling people who do have it, how their experience actually is?

(Excerpted from the original; full article via the source link below.)

This story hit the Hacker News front page today (207 points / 234 comments, via lwn.net). Our Tech Radar aggregates daily signals on AI engineering, backend architecture and DevOps — browse the related services and further reading below, or get in touch with our team.