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 56 (September 20, 2026)
Date: Wed, 23 Sep 2026 22:20:30 -0700 [thread overview]
Message-ID: <CAHt=NyO+T8bv0vT6VSbo2z_vYk=tjiAg+yKp+92Tb=uJO2OuBQ@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyNm+pC1spTw0E68jQXjE8K_im63KmrOT5SjdO8Y=ZYPQQ@mail.gmail.com>
GNU Tools Weekly News Week 56 (September 20, 2026)
Sorry I am a few days late.
Release updates for GNU toolchain:
* GDB 18.1.0 update
* https://inbox.sourceware.org/gdb-patches/87se32aoq1.fsf@redhat.com
* Release is this Friday!
GNU toolchain conference reminders:
* GNU Tools Cauldron 2026, Fri-Sun, October 2-4 (Prague, Czechia)
* https://gcc.gnu.org/wiki/cauldron2026
* https://conf.gnu-tools-cauldron.org/prg26/cfp
* Toolchains Track at LPC 2026, October 7th (Prague, Czechia)
* https://lpc.events/event/20/abstracts/
General/big GNU toolchain news (including sourceware news):
* Syncing Rust GCC ["JIT"] backend or how to test Murphy's law
* https://blog.guillaume-gomez.fr/articles/2026-09-22+Syncing+Rust+GCC+backend+or+how+to+test+Murphy%27s+law
* Meeting minutes - Office Hours for the GNU Toolchain - 2026-09-17
* https://inbox.sourceware.org/gcc/190c0f1d-cbe9-4fe2-be74-58c6042667b1@redhat.com/
* https://gcc.gnu.org/wiki/OfficeHours
*
GCC easy issue to tackle of the week:
* `(a&-a) < 0` -> `a == INT_MIN`
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126627
* Reach out to Andrea Pinski <andrew.pinski@oss.qualcomm.com> for
mentoring on this issue.
* Previous ones are listed on https://gcc.gnu.org/wiki/EasyIssuesOfTheWeek
GCC commits:
* https://gcc.gnu.org/r17-4212 ... r17-4502 - 291 commits
* Improve saturated unsigned add detection
* https://gcc.gnu.org/r17-4218 https://gcc.gnu.org/r17-4219
* gccrs sync
* https://gcc.gnu.org/r17-4278 ... https://gcc.gnu.org/r17-4360
* Improve some code in std::vector::push_back
* https://gcc.gnu.org/r17-4377-ge548eb628c689e
https://gcc.gnu.org/r17-4378-gedb9556068ae47
* contrib, libcpp, libstdc++: Update to Unicode 18.0.0
* https://gcc.gnu.org/r17-4409-g20a1e5b5c5addc
* aarch64: Add support for FEAT_CMH atomic {store,load} intrinsics
* https://gcc.gnu.org/r17-4448-gd5a076158aa3da
https://gcc.gnu.org/r17-4449-g4015b65b038bea
* phiopt: Better pre-vect heurstics for factoring out loads
* https://gcc.gnu.org/r17-4456-gb1dcde565577e8
* cselim: cond_if_else_store_replacement_limited support skipping on
store one either side
* https://gcc.gnu.org/r17-4469-ge35b8dad030bc4
GCC discussion:
*
GCC bugzilla stats
* 140 new issues filed
* 55 issues closed
binutils/gdb commits:
* RISC-V: Add Zama16b extension support
* https://sourceware.org/cgit/binutils-gdb/commit/?id=59db9002142a655b4d5e4af7cbf0605aaddefc7e
* RISC-V: Add support for ziccamoc extension.
* https://sourceware.org/cgit/binutils-gdb/commit/?id=cd2166234b9e6569b1cf8a4169e58f487996c447
gdb discussion:
*
binutils discussion:
*
glibc commits:
* aarch64: Add MTE mode tunable
* https://sourceware.org/cgit/glibc/commit/?id=8f6dfd399a97c77ea6855a5eb28a6babb81ec31c
* math: Update tanh from CORE-MATH
* https://sourceware.org/cgit/glibc/commit/?id=1c8c9998d803897d5765fab8c68ad9b0db6f7444
* malloc: Improve calloc
* https://sourceware.org/cgit/glibc/commit/?id=4b4de574ad95ffbee25b4aed3891275fd769ff3c
*
glibc discussion:
* glibc buildbot status
* https://inbox.sourceware.org/libc-alpha/20260920192938.GG2330@gnu.wildebeest.org/
next prev parent reply other threads:[~2026-09-24 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:06 GNU Tools Weekly News Week 53 (August 30, 2026) GNU Tools weekly via Gdb
2026-09-07 7:50 ` GNU Tools Weekly News Week 54 (September 6, 2026) GNU Tools weekly via Gdb
2026-09-15 1:05 ` GNU Tools Weekly News Week 55 (September 13, 2026) GNU Tools weekly via Gdb
2026-09-24 5:20 ` GNU Tools weekly via Gdb [this message]
2026-09-28 7:38 ` GNU Tools Weekly News Week 57 (September 27, 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=NyO+T8bv0vT6VSbo2z_vYk=tjiAg+yKp+92Tb=uJO2OuBQ@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