From: GNU Tools weekly via Gdb <gdb@sourceware.org>
To: gcc@gcc.gnu.org, binutils@sourceware.org,
libc-alpha@sourceware.org, gdb@sourceware.org,
andrew.pinski@oss.qualcomm.com
Subject: GNU Tools Weekly News Week 10 (November 2, 2025)
Date: Sun, 2 Nov 2025 23:50:39 -0800 [thread overview]
Message-ID: <CAHt=NyPaAZhqc3WSi1_WMBr=uZmZL=Jc2jwgQibeR1n6xwqyKA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyMASMc-5h9zYqH1L3Scbx2oJ6i-RzAS7Eb-WPbQqCmyuQ@mail.gmail.com>
GNU Tools Weekly News Week 10 (November 2, 2025)
General/big GNU toolchain news (including sourceware news):
* The GCC Steering Committee has a wiki page detailing their mission
and current requests are listed
** https://gcc.gnu.org/wiki/gcc-steering-committee
* Sourceware infrastructure community updates for Q3 2025
** Includes an update on forge
** https://inbox.sourceware.org/gcc/20251029104337.GN26406@gnu.wildebeest.org/T/#u
* Office Hours for the GNU Toolchain was held on October 30, 2025
** Notes from the call can be found at https://gcc.gnu.org/wiki/OfficeHours
* RISCV GCC: ABI breakage with fixed-length vector arguments
GCC discussion:
* GCC Wiki Warning History
** https://inbox.sourceware.org/gcc/CAF9ehCWJbihdCAV1xEeW2jrSJ12q=H-6=xH4EFtuOkfL4xxM9w@mail.gmail.com/T/#t
** https://gcc.gnu.org/wiki/WarningHistory
* a new version of `C: implement defer statements as per ts 25755` was posted
** https://inbox.sourceware.org/gcc-patches/20251027231813.954-1-navi@vlhl.dev/T/#t
GCC commits:
* Rust/gccrs: 143 commits sync up
* Ada/GNAT: 19 commit sync up
* C: Add GNU extension allowing compound literals of variable size
* Start to fix toplevel inline-asm with LTO
* libstd++ (library side): Implement C++23 P2674R1 - A trait for
implicit lifetime types
* Use the ranger in niter (helps with ctz loops)
* RISC-V: Implement standard fixed-length vector calling convention variant
GCC bugzilla stats
* 97 new issues filed
* 90 issues closed
glibc commits:
* More fixes for compiling glibc with clang
gdb discussion:
* test gdb as it runs qemu simulator
** https://inbox.sourceware.org/gdb/874irebykq.fsf@tromey.com/T/#mc83281aa015bbf793fb2372363848bb1ad7fe403
binutils discussion:
* continued GNU Tools Cauldron SFrame talk notes
** https://inbox.sourceware.org/binutils/933bbc83-5732-4655-870c-4c50b3742637@oracle.com/
** Also related LLVM discussion about adding SFrame support:
https://discourse.llvm.org/t/rfc-adding-sframe-support-to-llvm/86900
next prev parent reply other threads:[~2025-11-03 7:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 5:44 GNU Tools Weekly News Week 2 (September 7, 2025) GNU Tools weekly via Gdb
2025-09-14 21:19 ` GNU Tools Weekly News Week 3 (September 14, 2025) GNU Tools weekly via Gdb
2025-09-22 3:43 ` GNU Tools Weekly News Week 4 (September 21, 2025) GNU Tools weekly via Gdb
[not found] ` <CAHt=NyNKa=eQ8ytymevK-r_Zz5p_DhzOzpYC35YLdqzJ4XhgMQ@mail.gmail.com>
2025-10-13 0:47 ` GNU Tools Weekly News Week 7 (October 12, 2025) GNU Tools weekly via Gdb
2025-10-20 7:58 ` GNU Tools Weekly News Week 8 (October 19, 2025) GNU Tools weekly via Gdb
2025-10-27 4:38 ` GNU Tools Weekly News Week 9 (October 26, 2025) GNU Tools weekly via Gdb
2025-11-03 7:50 ` GNU Tools weekly via Gdb [this message]
2025-11-14 0:43 ` GNU Tools Weekly News Week 11 (November 9, 2025) GNU Tools weekly via Gdb
2025-11-14 0:51 ` GNU Tools weekly via Gdb
2025-11-17 7:00 ` GNU Tools Weekly News Week 12 (November 16, 2025) GNU Tools weekly via Gdb
2025-11-24 5:49 ` GNU Tools Weekly News Week 13 (November 23, 2025) GNU Tools weekly via Gdb
2025-12-01 6:45 ` GNU Tools Weekly News Week 14 (November 30, 2025) GNU Tools weekly via Gdb
2025-12-08 8:54 ` GNU Tools Weekly News Week 15 (December 7, 2025) GNU Tools weekly via Gdb
2025-12-15 7:32 ` GNU Tools Weekly News Week 16 (December 14, 2025) GNU Tools weekly via Gdb
2025-12-22 8:51 ` GNU Tools Weekly News Week 17 (December 21, 2025) GNU Tools weekly via Gdb
2025-12-28 19:51 ` GNU Tools Weekly News Week 18 (December 28, 2025) GNU Tools weekly via Gdb
2026-01-05 8:20 ` GNU Tools Weekly News Week 19 (January 5, 2026) GNU Tools weekly via Gdb
2026-01-12 8:42 ` GNU Tools Weekly News Week 20 (January 11, 2026) GNU Tools weekly via Gdb
2026-01-19 8:46 ` GNU Tools Weekly News Week 21 (January 18, 2026) GNU Tools weekly via Gdb
2026-01-26 7:21 ` GNU Tools Weekly News Week 22 (January 25, 2026) GNU Tools weekly via Gdb
2026-02-02 10:19 ` GNU Tools Weekly News Week 23 (February 1, 2026) GNU Tools weekly via Gdb
2026-02-09 8:16 ` GNU Tools Weekly News Week 24 (February 8, 2026) GNU Tools weekly via Gdb
2026-02-16 5:32 ` GNU Tools Weekly News Week 25 (February 15, 2026) GNU Tools weekly via Gdb
2026-02-23 6:43 ` GNU Tools Weekly News Week 26 (February 22, 2026) GNU Tools weekly via Gdb
2026-03-02 6:38 ` GNU Tools Weekly News Week 27 (March 1, 2026) GNU Tools weekly via Gdb
2026-03-09 7:51 ` GNU Tools Weekly News Week 28 (March 8, 2026) GNU Tools weekly via Gdb
2026-03-16 5:33 ` GNU Tools Weekly News Week 29 (March 15, 2026) GNU Tools weekly via Gdb
2026-03-23 19:40 ` GNU Tools Weekly News Week 30 (March 22, 2026) GNU Tools weekly via Gdb
2026-03-30 11:36 ` GNU Tools Weekly News Week 31 (March 29, 2026) GNU Tools weekly via Gdb
2026-04-06 8:57 ` GNU Tools Weekly News Week 32 (April 5, 2026) GNU Tools weekly via Gdb
2026-04-13 6:06 ` GNU Tools Weekly News Week 33 (April 12, 2026) GNU Tools weekly 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='CAHt=NyPaAZhqc3WSi1_WMBr=uZmZL=Jc2jwgQibeR1n6xwqyKA@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gnutoolsweekly@gmail.com \
--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