From: Collin Funk via Gdb <gdb@sourceware.org>
To: Joseph Myers <josmyers@redhat.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Andrew Pinski <pinskia@gmail.com>,
Carlos O'Donell <carlos@redhat.com>,
Gokhan <kadirgokhann@gmail.com>,
glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Tue, 16 Jun 2026 09:44:42 -0700 [thread overview]
Message-ID: <87a4subfk5.fsf@gmail.com> (raw)
In-Reply-To: <f0bd7f76-3917-dbf6-d731-fb1d0cae482d@redhat.com>
Joseph Myers <josmyers@redhat.com> writes:
>> 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.
>
> scripts/documented.sh is *extremely* outdated (see the linuxthreads
> reference) but might be a basis for generating a newer list of
> undocumented functions. Note that a lot of undocumented functions have
> bugs open in Bugzilla, so when documenting something, look to see if there
> is a bug to close.
+1, agreed.
>> 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.
>
> Collin should have C23 support for conform/, but maybe it was based on
> what glibc supported at a particular time rather than on exactly what's in
> the standard.
I think I only made C23 equivalent to C11. Finishing the C23 conform
tests would be nice, but it is quite tedious. E.g., when I tried to add
stdint.h/inttypes.h conform tests, you mentioned that many platforms do
not yet support _BitInt [1]. There is another issue that not all
supported compilers support '-std=c23'. A new contributor could probably
figure all of this out, but I would be very surprised if they found it
enjoyable. :)
Collin
[1] https://inbox.sourceware.org/libc-alpha/fc312bc5-56b2-e9ee-6e89-476d02d91687@redhat.com/
next prev parent reply other threads:[~2026-06-16 16:46 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
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 [this message]
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=87a4subfk5.fsf@gmail.com \
--to=gdb@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=collin.funk1@gmail.com \
--cc=josmyers@redhat.com \
--cc=kadirgokhann@gmail.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