From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: glibc developers <libc-alpha@sourceware.org>,
gcc developers <gcc@gcc.gnu.org>,
binutils developers <binutils@sourceware.org>,
gdb developers <gdb@sourceware.org>
Subject: Meeting Minutes - Office Hours for the GNU Toolchain - 2026-08-20
Date: Thu, 20 Aug 2026 19:53:35 -0400 [thread overview]
Message-ID: <e6206e50-a3e6-428f-965f-eee240a9b3a0@redhat.com> (raw)
There are Office Hours for the GNU Toolchain every 3rd Thursday!
Please see https://gcc.gnu.org/wiki/OfficeHours for more details.
The following was the agenda and discussions for both office hours:
Meeting: 2026-08-20 @ 1100h EST5EDT
Attendees: Carlos, David, David Malcolm, Jason Merrill, Andrew Stubbs, Claudio Bantaloukas, Martin Jambor, Richard Earnshaw, Saurov Shyam.
Agenda:
David Malcolm: I won't be able to attend Cauldron, can I present remotely?
Carlos: I can take the issue to the Cauldron Organizing Committee for next Friday the 28th and see what we can do. We might be able to accomodate a single presenter.
David Edelsohn: A virtual presentation is OK, but a hybrid conference is much harder.
Richard: Yes, hybrid poses problems, sometimes making the in-person conference more difficult.
David Malcolm: GSOC 24th deadline?
Martin: Student submission deadline is the 24th, and mentor deadline is the 31st. Extensions no longer possible.
Carlos: Did the new GCC AI policy help GSOC students?
Martin: No, all hand written, but in some cases external code e.g. eBPF programs could be written by LLMs.
Surya has a topic to present for Cauldron, but unfortunately due to travel restrictions she couldn't attend. So if virtual presentation work it would be fantastic. The other option is can be proxy, if someone can volunteer to present on behalf. The same has been suggested by Maxim today morning call (Asia).
ACTION: Carlos to reach out to OC to discuss.
David Malcolm: I submitted bugs that had llm-generated content, but I reviewed them before submitting.
Jason: Absolutely sounds "considered."
Richard: Would the other projects adopt the GCC AI policy?
Carlos: Yes, I would like to propose glibc accept it too, and I'll take the action item to reach out to and talk to Nick Clifton about it for binutils.
ACTION: Carlos to reach out to Nick.
Richard: Would it be possible to spend some Cauldron funding to record Office Hour talks and put them up as videos?
Carlos: Yes, but we'd have to discuss this with Sponsors and the Cauldron CIC directors, and maybe make them "micro-Cauldron talks" where we record talks throughout the year and upload them. This would need adding to the prospectus.
ACTION: Richard to send email to organizers to discuss this option.
Meeting: 2026-08-20 @ 0900h "Asia/Kolkata"
Attending: Dhruv, Maxim, Prachi, Soumya, Ramana, Manjunath, Surya, Saurov
Topics
What interesting technical topics would people like to present on / listen to ?
Maxim : Are there interesting areas in the backend / scheduler - Dispatch scheduling is an interesting area. we saw gromacs benefits.
Dhruv: It would be good to have a presentation about testsuite architecture and how it is structured ?
Maxim can share a few interesting bits about testsuite -- next office hours meeting Parallelization of testsuite
Ramana: Ask Kugan to present on AutoFDO
Prachi -- yes, should be good
Surya - KCFI patches from Kees - since this in
Surya - Is there a possibility for remote presentation at Cauldron ? this year it seems difficult - however we can and should use the office hours for such technical presentations. If we need to create more office hours to accommodate such presentations we are happy to do so.
Maxim - Sep Office hours Test-suite presentation , architecture and interesting facts.
Surya - October office hours , Shrink wrapping and intertwining with RA
Backlog
Kugan Autofdo
Andrea Pinski - Triaging a bug.
--
Cheers,
Carlos.
reply other threads:[~2026-08-20 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e6206e50-a3e6-428f-965f-eee240a9b3a0@redhat.com \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
/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