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 50 (August 9, 2026)
Date: Sun, 9 Aug 2026 22:35:47 -0700 [thread overview]
Message-ID: <CAHt=NyPX-HHC12UaO2X0yy8kadYpVSsnExwy2vLWDf8J9L2xHA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyNyiBc9FmCtMMPRzg71BSUFnNKHiMpkPR_QoT2VR6ncDQ@mail.gmail.com>
GNU Tools Weekly News Week 50 (August 9, 2026)
Release updates for GNU toolchain:
* GCC 16.2.0 was released!
* https://inbox.sourceware.org/gcc/r8p34qp8-r1qq-9nn3-r499-1q833r6801n4@fhfr.qr/
* status: https://inbox.sourceware.org/gcc/3s8pqo7q-s5qp-21r1-6qpo-6n8srp3rpsn4@fhfr.qr/
* GCC 14.5.0 is planed to be released on Sep 11th (RC1 on Sep 4th)
* https://inbox.sourceware.org/gcc/anWnjIo15_2FrBEf@tucnak/
* GDB 18 release branch was created
* https://inbox.sourceware.org/gdb/announce.6a74bc19.18b7d65e.395d2.50a7@mx.google.com/
* with a prelease was created
* https://inbox.sourceware.org/gdb-patches/6a74ce98.f1a44df3.162c5d.ceef@mx.google.com/
*
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
* cfp closes August 31st
* Toolchains Track at LPC 2026, October 7th (Prague, Czechia)
* https://lpc.events/event/20/abstracts/
General/big GNU toolchain news (including sourceware news):
* Michael Meissner appointed PowerPC port co-maintainer (GCC)
* https://inbox.sourceware.org/gcc/CADzB+2=8CJoq4g=tDA14mUcMs4B6wEwPUM6Rjkbv+vx+058_zQ@mail.gmail.com/
* Surya Kumari Jangala appointed PowerPC reviewer (GCC)
* https://inbox.sourceware.org/gcc/CADzB+2mLbJR7XhmS46YQD0DCXxjV8qJNF3DdcX3ZJ29Ny0wtCA@mail.gmail.com/
* Pierre-Emmanuel Patry appointed Rust Front End maintainer (GCC)
* https://inbox.sourceware.org/gcc/CAGWvnymaTEBMLw2o6N=oeSk_aQVs=wtsffS5gaVsouL5Ar9XLw@mail.gmail.com/
GCC easy issue to tackle of the week:
* a/b -> 1 if it is known that `a==b` in VRP without DOM
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126745
* this is a non-match one but the patch for this one should be
around 5-6 lines for the new method that gets added
* 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-2890 ... r17-3172 283 commits
* frange - sub-ranges
* https://gcc.gnu.org/r17-2891 https://gcc.gnu.org/r17-2892
https://gcc.gnu.org/r17-2898
* https://gcc.gnu.org/r17-2928 https://gcc.gnu.org/r17-2929
https://gcc.gnu.org/r17-3038
* https://gcc.gnu.org/r17-3041 https://gcc.gnu.org/r17-3042
https://gcc.gnu.org/r17-3043
* https://gcc.gnu.org/r17-3055 https://gcc.gnu.org/r17-3147
https://gcc.gnu.org/r17-3148
* https://gcc.gnu.org/r17-3162 https://gcc.gnu.org/r17-3163
* match: Simplify `(A | C) == A` to `(A & C) != 0` when C is power of 2
* https://gcc.gnu.org/r17-2916-g372d44c5611ecc
* Week 27th easy issue of the week
* scheduler compile time improvements
* https://gcc.gnu.org/r17-2919 ... r17-2922
* phiopt: Add some TARGET_MEM_REF support to factoring of loads
* https://gcc.gnu.org/r17-2955-g1a751916c6d506
* expand: Split divisions with near-power-of-two divisors
* https://gcc.gnu.org/r17-2970-g298071eb7e88b0
* Fix --enable-gather-detailed-mem-stats for PCH
* https://gcc.gnu.org/r17-2968-g60623805437fc7
* Oldest bug fixed for GCC 17 so far
* match: Recognize add/sub absolute-value idiom
* https://gcc.gnu.org/r17-2972-g36990bb0d14c48
* 10+ year old bug
* RISC-V: Implement reassociation width hook
* https://gcc.gnu.org/r17-3000-ge0e794b089a127
* Implement C++29 P3733R1 - More named universal character escapes
* https://gcc.gnu.org/r17-3022-g72c343684eb8d2
* GCC rs merge
* 78 commits
* https://gcc.gnu.org/r17-3059 ... https://gcc.gnu.org/r17-3136
* OpenMP: Use VOID_TYPE_P to check for void return type in SIMD
function clones.
* Week 44 easy issue
* https://gcc.gnu.org/r17-3156-ge212f5ef86f1a8
* gimplefe: Add support for REF_REVERSE_STORAGE_ORDER on mem
* https://gcc.gnu.org/r17-3169-gfbdabd5f9a27c8
* Improve tree_expr_nonnegative_p by using the ranger
* https://gcc.gnu.org/r17-3171-g5af52562e3fb59
GCC discussion:
* Changes in emails sent by the forge
* https://inbox.sourceware.org/gcc/d21bf3f0-38f5-42fe-9ffe-79ac1bf62565@arm.com/
* Proposed synchronisation of forge accounts with MAINTAINERS.yml
* https://inbox.sourceware.org/gcc/010c2e55-7f21-4819-8657-f2ad9eccd616@foss.arm.com/
GCC bugzilla stats
* 154 new issues filed
* 88 issues closed
binutils/gdb commits:
*
gdb discussion:
*
binutils discussion:
*
glibc commits:
*
glibc discussion:
* Hurd and trust relationship with file system translators
* https://inbox.sourceware.org/libc-alpha/87tsp528bj.fsf@oldenburg.str.redhat.com/
next prev parent reply other threads:[~2026-08-10 5:36 UTC|newest]
Thread overview: 51+ 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 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
2026-04-20 5:10 ` GNU Tools Weekly News Week 34 (April 19, 2026) GNU Tools weekly via Gdb
2026-04-25 23:52 ` GNU Tools Weekly News Week 35 (April 26, 2026) GNU Tools weekly via Gdb
2026-04-25 23:59 ` GNU Tools weekly via Gdb
2026-05-04 1:34 ` GNU Tools Weekly News Week 36 (May 3, 2026) GNU Tools weekly via Gdb
2026-05-06 8:38 ` Jose E. Marchesi via Gdb
2026-05-11 6:15 ` GNU Tools Weekly News Week 37 (May 10, 2026) GNU Tools weekly via Gdb
2026-05-18 9:39 ` GNU Tools Weekly News Week 38 (May 17, 2026) GNU Tools weekly via Gdb
2026-05-25 5:47 ` GNU Tools Weekly News Week 39 (May 24, 2026) GNU Tools weekly via Gdb
2026-05-31 16:39 ` GNU Tools Weekly News Week 40 (May 31, 2026) GNU Tools weekly via Gdb
2026-06-08 20:56 ` GNU Tools Weekly News Week 41 (June 7, 2026) GNU Tools weekly via Gdb
2026-06-15 7:21 ` GNU Tools Weekly News Week 42 (June 14, 2026) GNU Tools weekly via Gdb
2026-06-22 5:21 ` GNU Tools Weekly News Week 43 (June 21, 2026) GNU Tools weekly via Gdb
2026-06-28 21:24 ` GNU Tools Weekly News Week 44 (June 28, 2026) GNU Tools weekly via Gdb
2026-07-05 7:19 ` GNU Tools Weekly News Week 45 (July 5, 2026) GNU Tools weekly via Gdb
2026-07-13 1:21 ` GNU Tools Weekly News Week 46 (July 12, 2026) GNU Tools weekly via Gdb
2026-07-20 23:22 ` GNU Tools Weekly News Week 47 (July 19, 2026) GNU Tools weekly via Gdb
2026-07-27 5:33 ` GNU Tools Weekly News Week 48 (July 26, 2026) GNU Tools weekly via Gdb
2026-08-03 1:19 ` GNU Tools Weekly News Week 49 (August 2, 2026) GNU Tools weekly via Gdb
2026-08-10 5:35 ` GNU Tools weekly via Gdb [this message]
2026-08-17 21:41 ` GNU Tools Weekly News Week 51 (August 16, 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=NyPX-HHC12UaO2X0yy8kadYpVSsnExwy2vLWDf8J9L2xHA@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