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 7 (October 12, 2025)
Date: Sun, 12 Oct 2025 17:47:47 -0700 [thread overview]
Message-ID: <CAHt=NyNXXPShoxuBUdL5zK_XMU4tkjnuf00C_3Sgor9pOQEiVA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyNKa=eQ8ytymevK-r_Zz5p_DhzOzpYC35YLdqzJ4XhgMQ@mail.gmail.com>
GNU Tools Weekly News Update Week 7 (October 12, 2025)
General/big GNU toolchain news (including sourceware news):
* Sourceware Open Office was held on Friday October 10th
* Videos of the 2025 GNU tools Cauldron are now published on youtube
** https://www.youtube.com/playlist?list=PL_GiHdX17WtxuKn7QYme8EfbBS-RKSn0w
** https://gcc.gnu.org/wiki/cauldron2025
* LWN.net has a few write ups about the GNU tools Cauldron
** GCCrs after libcore - https://lwn.net/Articles/1040197/
** Next steps for BPF support in the GNU toolchain -
https://lwn.net/Articles/1039827/
** Kernel hackers at Cauldron, 2025 edition - https://lwn.net/Articles/1039784/
* GCC 16 stage 3 starts Nov. 17th and GCC 16 status was posted
** https://inbox.sourceware.org/gcc/q5nop2q5-n0nr-7622-o39r-o116271p79n9@fhfr.qr/
* GDB 17.1 release update -- 2025-10-11
** https://inbox.sourceware.org/gdb-patches/aOrnv83K4oE0cdbV@adacore.com/
GCC discussion:
* RFC: Debug info for coroutine suspension locations
** https://inbox.sourceware.org/gcc/CAB6OZBHVoqDyT+KD+x_u6mM96Brr82+1L0pSBy8y+d-wu2DZGA@mail.gmail.com/
* RFD: labels for GCC in the forge
** https://inbox.sourceware.org/gcc/5675fa61-3aaf-4763-be22-002616ed1bc8@arm.com/
* Notes from Cauldron 2025 GCC GSoC BoF
** https://inbox.sourceware.org/gcc/ri6ecrdz5eh.fsf@virgil.suse.cz/
GCC commits:
* Improve vectorization of bool types
* AVR: Speed up floating point comparisons
* Handle commonization of trailing stores earlier
* c: Implement C2y handling of incomplete tentative definitions
* c: Allow variably-modified types in generic associations for C2Y
(part of N3348)
* c++: C++26 va_start - part of P3348R4
* libstdc++: Implement strided_slice, full_extent_t.,
submdspan_mapping_result from <mdspan> (N5014)
* libstdc++: Implement std::layout_left_padded and
std::layout_right_padded (N5014)
* libstdc++: Implement P3107R5 and P3235R3 optimizations for std::print
* aarch64: Improve Apple M3 cores, add M4
* Add a simple DSE to help out early code generation
* AVR: Allow target to chose address-space for artificial rodata
(switch to lookup tables)
GCC bugzilla stats
* 94 new issues filed
* 85 issues closed
glibc commits:
* ppc64le: optimized strcmp and strncmp for power10
* x86: Detect Intel Nova Lake and Wildcat Lake Processors
gdb/binutils commits:
* aarch64: Add GICv5 system registers support for binutils
* aarch64: Add SME_TMOP, SME_MOP4, SSVE_FEXPA, and SSVE_BITPERM
support for binutils
binutils discussion:
* GNU Tools Cauldron SFrame talk notes
** https://inbox.sourceware.org/binutils/933bbc83-5732-4655-870c-4c50b3742637@oracle.com/
next prev parent reply other threads:[~2025-10-13 0:49 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 via Gdb [this message]
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 News Week 10 (November 2, 2025) GNU Tools weekly via Gdb
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=NyNXXPShoxuBUdL5zK_XMU4tkjnuf00C_3Sgor9pOQEiVA@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