From: GNU Tools weekly via Gdb <gdb@sourceware.org>
To: gcc@gcc.gnu.org, binutils@sourceware.org,
libc-alpha@sourceware.org, gdb@sourceware.org
Cc: andrew.pinski@oss.qualcomm.com
Subject: GNU Tools Weekly News Week 3 (September 14, 2025)
Date: Sun, 14 Sep 2025 14:19:20 -0700 [thread overview]
Message-ID: <CAHt=NyPnAeEzUoCVUFVDErpM7C+ieaNti8HxSwi-nJD-anSBuQ@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyPpC47e6400=ZxqwJ5W5B2ABmhUZk+SWsRKSTdxVu4SVA@mail.gmail.com>
GNU Tools Weekly News Update Week 3 (September 14, 2025)
General/big GNU toolchain news (including sourceware news):
The GNU tools Cauldron 2025 schedule is now live:
https://conf.gnu-tools-cauldron.org/opo25/schedule/
Sourceware Together; Open Office was held on Friday September 12th
gccrs August 2025 Monthly report:
https://inbox.sourceware.org/gcc/1a8ba586-89c7-4a3a-b16e-4757fed460c1@embecosm.com/T/#u
GCC discussion:
* Should the forge-bot send patches to the gcc-patches mailing list?
https://inbox.sourceware.org/overseers/20250909215535.GO19968@gnu.wildebeest.org/T/
* Attribute for custom memset function:
https://inbox.sourceware.org/gcc/CAH6eHdSdx4nd=hyyQGjzfc2GOLmM=E1w8PGBC++5zBWaZ=ZKfw@mail.gmail.com/T/
* RISC-V nightly performance testing of GCC on SPEC CPU 2017:
https://inbox.sourceware.org/gcc/4ED897B6-0F37-4954-A18F-47EC768F9808@igalia.com/T/
* Clarification about RTL shifts semantics:
https://inbox.sourceware.org/gcc/87y0qk27sc.fsf@googlemail.com/T/
GCC commits:
* Improve the malloc+memset->calloc optimization (not doing as much
and doing more)
* C++26: libstdc++: Implement constant_wrapper, cw from P2781R9.
* C++26: libstdc++: Adjust span/mdspan CTAD for P2781R9.
* C++26: libstdc++: Apply LWG4351 to CTAD of span/mdspan.
* c++: Fix mangling of _Float16 template args
* c, c++: Allow &__real__ static_var in constant expressions
* c++20: Change mangling of Intel/Motorola extended long double
literals ** ABI CHANGE**
* c: Warn when returning nested functions that require a non-local context.
* new fabs(a+0.0) -> fabs(a) pattern (From a first time contributor)
* c2y:: Implement N3517 array subscripting without decay
* ~70 commits to the Ada front-end
GCC bugzilla stats:
* 97 new issues filed
* 64 issues closed
glibc commits:
* Fix build for -Os for a few targets
* AArch64: add optimised strspn/strcspn
* Use builtin atomics more
* benchtests: Add lgamma, asinh, and acosh benchmarks
gdb/binutils discussion:
* gdb XML type for SME ZA storage:
https://inbox.sourceware.org/gdb/CANnS9ruMH-VeRN+SXrP2uOxkMg=mDTZWab=3R7-77Aa8apGEFQ@mail.gmail.com/T/
* GDB 17 pre-release (first prelease for GDB 17 before RCs) for
testing: https://inbox.sourceware.org/gdb-patches/86y0qku8qm.fsf@gnu.org/T/
* Removal of stabs debug info support in GDB:
https://inbox.sourceware.org/gdb-patches/20250910203035.1702632-1-guinevere@redhat.com/T/
next prev parent reply other threads:[~2025-09-14 21:23 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 via Gdb [this message]
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 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=NyPnAeEzUoCVUFVDErpM7C+ieaNti8HxSwi-nJD-anSBuQ@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