From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ypgLHaiGMGo5FAkAWB0awg (envelope-from ) for ; Mon, 15 Jun 2026 19:11:36 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=svbS0Bt6; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 677B81E070; Mon, 15 Jun 2026 19:11:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [38.145.34.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 826591E070 for ; Mon, 15 Jun 2026 19:11:35 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 01B1C48FDCA8 for ; Mon, 15 Jun 2026 23:11:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 01B1C48FDCA8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1781565095; bh=yXmlefaS7UqCwY0K8+hWgW11o6W9qZ9iJdPvprW1ef8=; h=Date:Subject:To:Cc:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=svbS0Bt6AWWE4z3y+UN7CBNA4oF0V6cXJQWDdJBTc6gB461T4Tgmm72gx0aRRZacY ZjmcbGxDy1f3LtKlTWikofKAZVJtu4GcoDaQNIQVKcBhj5Z1geRBgjQjbwnIn/w7zq 9TEG0C2yu6GWh6LCGxYkmceEH8pa6Z0TdX1i71ys= Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) by sourceware.org (Postfix) with ESMTPS id BA46348FDCAD for ; Mon, 15 Jun 2026 23:11:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BA46348FDCAD ARC-Filter: OpenARC Filter v1.0.0 sourceware.org BA46348FDCAD ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1781565060; cv=none; b=gm54fMpQ94WjPZBqUq5nLE/E2Wk6vzmEq7DgspJKyc4tEuTtqObT123NhDXHrr9L51ctYnoPIej4uvgvrcOVh2mPWJqWcH57pKSgKwJAYsZ06IKbEOVYobj36VVk3z8EQw7RyXv5VymPGmDc12Et8Gh0F0Dj2xPlG5Y4cENCadM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1781565060; c=relaxed/simple; bh=jK1UKFQ49tW+WTjwbwCGprICeti9x9Vf+nUjjc6V++g=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=MxqEDo518MPe4/DCnd7ox7Tnu8rCohsNx2KVB03qU+eMt2qGyPANuNg6vg/qI7+9MyIOYYETCGtDwDqRiMY+44v/vifalzePtAXJnpqr4aAADYwFV2lwwfVFtaKlWfVA7pfriuYhAj+5LkxWHsI5O5QtW2fobZ7sgikGR9O12S4= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=linaro.org header.i=@linaro.org header.a=rsa-sha256 header.s=google header.b=RqYJbyI1 DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BA46348FDCAD Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-8ce9df49c5fso61906926d6.1 for ; Mon, 15 Jun 2026 16:11:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1781565060; x=1782169860; h=content-transfer-encoding:in-reply-to:organization:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yXmlefaS7UqCwY0K8+hWgW11o6W9qZ9iJdPvprW1ef8=; b=qpGpkyYbipzXwgLazw7HfeHtlbZ6iR0jEjtdhTKiNthvoJqla46z20qabKymj96nvP dV0eZw/GFevOnxmw+Jm+8JIDBw7iGTtZraxPcPBvRrHXj/kePOejWCxrE2loUkj10VLQ zcxJaepHwzXCFsyjeI56SnWo2N/G/tZpZohjnNcX4zD+6yxMQEdgLyqMplF2Mk88Ro1h sw03TRSLZo7BAo4zcmY9OdnQvL6dEHXsKsG6MHUlLrF3jUwdreJOifB87vfDlZ4gepek e8E1E1BBeQC0Vi6xkm2YLN+pE1LwYfeDaeARgvuolL4XL7qLVVJAd+Cw2MV2HtqQgFBA Te3g== X-Forwarded-Encrypted: i=1; AFNElJ/U8VBIXcogmdn3kac4lUoGRRyJVWaIELHZOGUuyMcyMpzo04Eiz52tINFT059BOPLOdnw=@sourceware.org X-Gm-Message-State: AOJu0YxLbN9n6kBz7QmmECfc0dh+Tmprwn3Qzn9zhTibywGEINN+Ht8+ h+WccHLGKnRUoJTAaFIZB8/Kj/aHy/7ppf4OJ8//0/AX+KtrU/tH135rdsaoh3W/PwY= X-Gm-Gg: Acq92OFC6SBJ/4IeJIkRwuaTrAaHNUz62kZgRtP47krnOKu8qt8kgLO9G2B/dFGCbAS FdL949mp1cZ4UATcv3c/SqEkEUOihCMDKCVMdBv5tYyxwOCmCMrdt3uglVZF//FXTet/3p3f3xG M9j80gyzn66OSs/Og5rpK7mwJ3nelAhbh1jkDa3Q/YvZ+YANbBamoWgku1kwVf83rlBeNh3DaAi R0RhNoTqOaVZEQcn9nn/uqFoAmRTnNn5Tl3HBZfeltMybyKNJIk2mMsOCQrlUvMLYg2q4oTun9h 7WOS78gcslX/ylH03Q3gDh2FXmzr7SXOO7GFI90eLk649nDkjlQoY2zFwgmI4rbYydOdmfVafqL 71lzbhnSQibpAVu6YTMecofm7cXNh0MyKlpYJ6zi7xPTLiwwF+Q6gMO+uNzAi+LFw3AqV41OhQO wGXkTfrMxSKgJ1jNk3tRTLEngA50lM+AWl/TaFs7ktZJq1nRsKaqZiIyOkmOP+1j/5TuonFgIE1 phHPRZFbrihTee94edFpHhSV5G5n0sUtQ== X-Received: by 2002:a05:620a:468e:b0:915:9f87:eae6 with SMTP id af79cd13be357-917f1f4be03mr2155752685a.42.1781565059910; Mon, 15 Jun 2026 16:10:59 -0700 (PDT) Received: from ?IPV6:2804:1b3:a7c0:41cc:fc5e:9ba0:26eb:da54? ([2804:1b3:a7c0:41cc:fc5e:9ba0:26eb:da54]) by smtp.gmail.com with ESMTPSA id af79cd13be357-9161a006ef0sm1218324485a.24.2026.06.15.16.10.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Jun 2026 16:10:57 -0700 (PDT) Message-ID: <12079c45-5246-49a2-9c95-e581cbbc20b5@linaro.org> Date: Mon, 15 Jun 2026 20:10:53 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: =?UTF-8?Q?Re=3A_Nominations_for_Anthropic=E2=80=99s_Claude_for_Open?= =?UTF-8?Q?_Source_program?= To: Andrew Pinski , Carlos O'Donell , Gokhan Cc: Collin Funk , glibc developers , gdb developers References: <5c2e18dd-807c-4331-b12c-a5b17b256f5b@linaro.org> <87ecibxqyf.fsf@gmail.com> <5452704c-c160-425a-9e7c-af33f66617f0@redhat.com> Content-Language: en-US Organization: Linaro In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Adhemerval Zanella Netto via Gdb Reply-To: Adhemerval Zanella Netto Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 15/06/26 18:35, Andrew Pinski wrote: > On Mon, Jun 15, 2026 at 2:17 PM Carlos O'Donell wrote: >> If anything in the face of LLMs I want to double down on actively >> mentoring more developers to FOSS development. > > When a newcoming came in asking for things to do last month, what was > given is most likely overwheling for them and never responded again. > https://inbox.sourceware.org/libc-alpha/CAFPohwASPGQHreidwNTR3Eo81f_TfsajkF0sH2qZFKqSUQ47mg@mail.gmail.com/ Sorry if I was too brief and potentially not welcoming; I could have spent some time digging into potential work and writing down better ideas. So I will take the opportunity and write them down: 1. Testing The testing would aim to both improve libsupport (the support/ subfolder) by consolidating internal functions (as LTP does for its testing) and add new tests to cover missing symbols or functionality. We now have container support, so we can extend testing for functionality that requires a more complex system setup. Also, check whether the tests can be improved in terms of coverage and/or time spent. I started focusing on this area, and it culminated in a patchset to improve test scalability [1]. One issue with this kind of work is that it requires a lot of GNU Make knowledge, but we do have many internal examples, especially new tests, on how to improve coverage and write better tests. One possible subproject is to document how to properly write glibc tests using libsupport and/or adapt the remaining one to use it. There are still around 30 tests that use the old test-skeleton.c - 12 in libio/, the rest scattered across stdlib, rt, resolv, posix, nptl, io. 2. Benchmarking Another possible project is to improve benchmarks (benchmark subfolder), which is currently cumbersome, quite hard to read, and somewhat difficult to parse. It would be really interesting to follow something like Google Benchmark [2], which has many terminal color gimmicks, but focuses on providing proper, meaningful information without the need for extra parsing or using the bench scripts. 3. Documentation Document undocumented functions in the manual. The manual/ has 55 .texi files and a long tail of installed functions with no entry. Pick a small family (e.g. some wcs*, mkostemp variants, newer C23 additions), write the texinfo. This also has zero ABI risk, and is easy to review. 4. Compiler-warning / new-GCC cleanups Build with a newer GCC or stricter flags and fix the warnings in one subdirectory. Bounded, and a good way to learn the -Werror discipline glibc enforces. Another possibility is to check which backports are required to enable the old release branch to build cleanly with newer GCC versions. 5. Add missing header annotations Check new gcc/clang annotations (__wur, __nonnull, __attribute_malloc__) and apply them where clearly correct. Small but needs care — must not introduce false-positive warnings in the test suite, which would teach the newcomer to actually run make check. 6. Internal script cleanup This might be a more contentious one, but I think we can reduce our build dependencies by at least rewriting the Perl script to either awk or Python. There are small (1 to 2 weeks' work) projects that I think are good for newcomers. Below are some medium-sized (2-6 weeks' work) projects that require some more internal knowledge and research: 7. C23 conformance gaps The implementation of C23 is nearly complete, so the remaining work is mostly conformance testing and coverage: cross-check against Joseph Myers's C23 status tracker on libc-alpha, find the few stragglers, and write the missing conform/ tests. Good intro to the standards machinery without needing to design new ABI. 8. Resolver/getaddrinfo test coverage using support/resolv_test.h Plenty of resolver behavior is under-tested; the framework lets a newcomer spin up a fake in-process DNS server. Medium because the domain is fiddly, but the tooling is already built. And I can work on mentoring if someone is willing to work on any of this work. > > I even pointed out in the news letter when referering to this email > that "this newsletter could use some easy issues of the week for glibc > and a mentor to reach out to for it": > https://inbox.sourceware.org/libc-alpha/CAHt=NyPLDnHzbsV8xc7TC9Us9Djg6sDMo+QqKpbg0Kgnp6MzRw@mail.gmail.com/ > Well, I did reach out to you, but your reply made it seem like you would take care of it yourself [3]. In any case, if you are will I can help you with the glibc side of the weekly news. > But nothing, not even saying let me get back to you on this. Not even > a word. So I don't see any double down on this at all from you. In > fact I just see inaction from you. > > Thanks, > Andrea [1] https://patchwork.sourceware.org/project/glibc/list/?series=62266 [2] https://github.com/google/benchmark [3] https://gcc.gnu.org/pipermail/gcc/2025-September/246616.html