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 15 (December 7, 2025)
Date: Mon, 8 Dec 2025 00:54:25 -0800 [thread overview]
Message-ID: <CAHt=NyMO-bGXqi_9QcWY6+QoUycSqFLipON6nw-KRTOJvS45pw@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyP8xPvZ3+Ugh9rzp2R=qcW+oxNcU3RgUQFdeVM7kHR9bA@mail.gmail.com>
GNU Tools Weekly News Week 15 (December 7, 2025)
Release updates for GNU toolchain:
* GDB 17.1 release next weekend (Sat-Sun Dec 13-14)
* https://inbox.sourceware.org/gdb-patches/aTWF5TvHxYpgR2kp@adacore.com/T/#u
* glibc 2.43 release planning
* https://inbox.sourceware.org/libc-alpha/f8fd8390-c481-4c3b-a270-31df08129bf0@redhat.com/T/
* https://sourceware.org/glibc/wiki/Release/2.43
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
* What’s New in Oracle Solaris 11.4 SRU 87
** GCC 15 included now
** https://blogs.oracle.com/solaris/whats-new-in-oracle-solaris-11-4-sru-87
GCC commits:
* Fixes for aarch64 mingw support (long double and varargs)
* MIPS: add support for mips allegrex cores
* GCC rust: 12 patch sync
* Ada: 7 patch sync
* Sync libsanitizer from upstream
* amdgcn: Implement Managed Memory
* libstdc++: implement P3044R2
* libstdc++: Convertibility of rank == 0 layouts, LWG4272.
* libstdc++: Implement P2655R3
* Add -ffuse-ops-with-volatile-access (enabled for x86 by default)
* OpenMP: C/C++ parser support for dyn_groupprivate
** Fortran support was earlier
GCC discussion:
* injected class name vs. constructor reference (with templates)
** https://inbox.sourceware.org/gcc/280584618.373279.1765122885363@connect.xfinity.com/T/#u
* "A: a new bug to old plain C"
** https://inbox.sourceware.org/gcc/CAKBShRQUB-YPq48UO_heX67j=-_2jpYWuxJKig+RC6B-mP5PJA@mail.gmail.com/T/#t
* Bug in identical code folding?
** https://inbox.sourceware.org/gcc/aa96c8d9-e2b4-46f5-aa43-73e1fded3804@gjlay.de/T/#t
* Question about ifcvt optimization
* https://inbox.sourceware.org/gcc/CAPt2h2YgxzSB+N8jmrjEW7yLr1+xXGj-EPuygVgEn65VwqydPg@mail.gmail.com/T/#u
GCC bugzilla stats
* 113 new issues filed
* 79 issues closed
glibc commits:
* aarch64: Optimise AdvSIMD log1pf, logf, log2f, log10f, log1p, log,
log2, log10
* aarch64: Optimise AdvSIMD acoshf, asinhf, atanhf
* aarch64: Implement AdvSIMD and SVE rsqrt(f) routines
glibc discussion:
* Deprecation of s390-32 in glibc
* https://inbox.sourceware.org/libc-alpha/b1dfec5f-54d1-49e8-a14d-b02bd79ee4d3@linux.ibm.com/T/
binutils/gdb commits:
* gdb/guile: remove support for Guile < 2.2
* Add AMD znver6 processor support
next prev parent reply other threads:[~2025-12-08 8:55 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 " 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 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 via Gdb [this message]
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=NyMO-bGXqi_9QcWY6+QoUycSqFLipON6nw-KRTOJvS45pw@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