Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto via Gdb <gdb@sourceware.org>
To: Andrew Pinski <pinskia@gmail.com>, Carlos O'Donell <carlos@redhat.com>
Cc: glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Fri, 12 Jun 2026 20:07:51 -0300	[thread overview]
Message-ID: <5c2e18dd-807c-4331-b12c-a5b17b256f5b@linaro.org> (raw)
In-Reply-To: <CA+=Sn1mzU_OrGaz8wbS3bNEf3ZZM9u6H0zY92hfR-99d8usFMA@mail.gmail.com>



On 12/06/26 16:29, Andrew Pinski wrote:
> 
> 
> On Fri, Jun 12, 2026, 12:19 PM Carlos O'Donell <carlos@redhat.com <mailto:carlos@redhat.com>> wrote:
> 
>     Developers,
> 
>     Anthropic is generously offering 6 months of Claude Max 20x to Free and Open
>     Source Software projects to support the FOSS ecosystem. These tools can be
>     incredibly helpful with reviewing upstream code, evaluating the conformance of
>     a particular interface to a standard, or just for your own learning and
>     exploring the implementation of the project or subsystem.
> 
>     If you are an established, active contributor to the GNU Toolchain and are
>     interested in having access to Claude Max 20x under Anthropic’s Claude for Open
>     Source program, please respond to this email thread with a short description of
>     how you would utilize the access and the potential impact on the GNU Toolchain.
>     The program's slots are limited and David Edelsohn and I plan to review the
>     proposals. Please keep in mind that these are individual grants from Anthropic
>     to you personally. If you are approved you’ll get an email from Anthropic with
>     further instructions.
> 
>     While the current GNU Project policy is not to accept LLM-generated content in
>     the projects, that still leaves other uses like bug triage, patch review, and
>     research as ways to use these tools.
> 
>     --
>     Cheers,
>     Carlos.
> 
>     P.S. This is not an endorsement of Anthropic, Claude or LLMs. We dislike
>     having to say it, but please don’t use this thread as a platform to express
>     your personal opinions about the companies or about AI’s impact on the world.
> 
> 
> Dont send out emails like this in the first place then.
> 
> Also note coverity has been offering similar services for code coverage and static analysis for years now. But there was no notice like that sent out for this. Why try to push llm when static analysis does the same?


gnulib guys seem to be experimenting with LLM for patch review recently [1],
and it has uncovered real regressions [2]. And I recall that their 
experience with Coverity has been subpar [3], and I think they even started 
disregarding it.

Personally, I see value in adding an LLM to the patch review phase, especially 
since we lack manpower and initial triage can help newcomers and uncover some 
issues.


[1] https://lists.gnu.org/archive/html/bug-gnulib/2026-06/msg00016.html
[2] https://lists.gnu.org/archive/html/bug-gnulib/2026-06/msg00037.html
[3] https://lists.gnu.org/archive/html/bug-gnulib/2019-05/msg00059.html

  parent reply	other threads:[~2026-06-12 23:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 19:18 Carlos O'Donell via Gdb
2026-06-12 19:29 ` Andrew Pinski via Gdb
2026-06-12 21:18   ` Carlos O'Donell via Gdb
2026-06-12 21:21     ` Andrew Pinski via Gdb
2026-06-12 23:07   ` Adhemerval Zanella Netto via Gdb [this message]
2026-06-12 23:11     ` Andrew Pinski via Gdb
2026-06-15 11:39       ` Mark Wielaard
2026-06-15 21:11         ` Carlos O'Donell via Gdb
2026-06-16 11:03           ` Mark Wielaard
2026-06-16 13:53             ` Carlos O'Donell via Gdb
2026-06-17 16:28               ` Alexandre Oliva via Gdb
2026-06-18  5:27                 ` Eli Zaretskii via Gdb
2026-06-18  6:59                   ` Alexandre Oliva via Gdb
2026-06-18  7:41                     ` Eli Zaretskii via Gdb
2026-06-18 13:43                       ` Alexandre Oliva via Gdb
2026-06-18 14:11                         ` Eli Zaretskii via Gdb
2026-06-18 14:44                         ` Jeffrey Walton via Gdb
2026-06-18 17:11                   ` Thomas Dineen via Gdb
2026-06-19 22:21                     ` Andy Wang via Gdb
2026-06-16 16:03             ` Siddhesh Poyarekar
2026-06-20  0:09           ` Carlos O'Donell via Gdb
2026-06-15 17:25       ` Siddhesh Poyarekar
2026-06-12 23:46     ` Collin Funk via Gdb
2026-06-13  1:15       ` Sam James via Gdb
2026-06-15 21:17       ` Carlos O'Donell via Gdb
2026-06-15 21:35         ` Andrew Pinski via Gdb
2026-06-15 23:10           ` Adhemerval Zanella Netto via Gdb
2026-06-16 14:50             ` Xi Ruoyao via Gdb
2026-06-16 14:59               ` Adhemerval Zanella Netto via Gdb
2026-06-16 17:49                 ` Carlos O'Donell via Gdb
2026-06-22 18:35                   ` Gokhan via Gdb
2026-06-16 16:22             ` Joseph Myers via Gdb
2026-06-16 16:44               ` Collin Funk via Gdb
2026-06-12 23:12 ` Sam James via Gdb
2026-06-15 21:19   ` Carlos O'Donell via Gdb
2026-06-16 16:08     ` Siddhesh Poyarekar
2026-06-16 16:36       ` Joseph Myers via Gdb
2026-06-16 18:01         ` Carlos O'Donell via Gdb
2026-06-13  0:19 ` Alexandre Oliva via Gdb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c2e18dd-807c-4331-b12c-a5b17b256f5b@linaro.org \
    --to=gdb@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=pinskia@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox