GCC AI Policy Announcement

[Arthur Cohen]

Hi Richard,

What are the important LLM issues that you think the policy fails to 
address? As the policy itself states, the it is expected to evolve and 
feedback is welcome. The goal is to continuously improve it.

Thanks,

Arthur

On 7/29/26 9:06 AM, Richard Biener wrote:
> On Wed, Jul 29, 2026 at 8:07 AM Teylu, Andrew via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> Long time listener, first time caller …
>>
>> For those of who don’t click through, the rough summary is: to decline any patches longer than 15 lines that are written by AI.
>>
>> Is anyone else surprised by this? When the threads first started on this topic earlier on, I had believed that GCC was “more optimistic” on the use of generative AI, but this new policy seems rather “anti AI” (a change of only 15 lines seems very limiting).
>>
>> To be clear, I am not trying to get the policy changed, I am just wondering if any other developers are surprised at this?
> 
> I'm not surprised that we take a conservative stance on copyright
> issues related to LLM contribution.  I'm somewhat
> surprised we're leaving open the grey area of "legally insignificant"
> contributions.  The cited 15 lines is not a hard
> number and is not directly referred to in the policy.
> 
> In the end the policy side-steps all important issues with LLM
> contributions by deflecting to legal issues ...
> 
> Richard.
> 
>> From: Gcc <gcc-bounces~andrew.jones=vector.com@gcc.gnu.org> on behalf of David Edelsohn via Gcc <gcc@gcc.gnu.org>
>> Date: Wednesday, 29 July 2026 at 03:12
>> To: GCC Development <gcc@gcc.gnu.org>; Jonathan Wakely <jwakely.gcc@gmail.com>
>> Subject: GCC AI Policy Announcement
>>
>> The GCC Steering Committee has accepted the recommended policy of the GCC
>> AI Policy Working Group.  The policy is described in the following document
>> preview / pull request in Forge, which will be committed to the GCC website:
>>
>> https://forge.sourceware.org/redi/gcc-wwwdocs/commit/4d0793a6a14bf9bfe9e92ac1599840780355199d
>>
>> We expect the policy to continue to evolve and will revisit it periodically.
>>
>> We wish to thank Jonathan Wakely for his leadership of the working group
>> and the members of the working group: Carlos O'Donell, Sudakshina Das, Jason
>> Merrill, Joel Sherrill, Sam James, Robin Dapp, and Arthur Cohen.
>>
>> Happy Hacking!
>> David

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x1B3465B044AD9C65.asc
Type: application/pgp-keys
Size: 3143 bytes
Desc: OpenPGP public key
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20260729/d9f9e940/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20260729/d9f9e940/attachment.sig>