Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 59 (October 11, 2026)
Date: Mon, 12 Oct 2026 00:19:49 -0700	[thread overview]
Message-ID: <CAHt=NyP7WhRpthBKDeQ0Mdmm9SuaoeWuDoL7=K6HEG8yAM9Fsg@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyN6s2wmSTh+zgE6WWQ6-eg1-Gvbj_5a1njqz3jM4LivDQ@mail.gmail.com>

GNU Tools Weekly News Week 59 (October 11, 2026)
Note week 58 was the week of the cauldron

Release updates for GNU toolchain:
 * None

General/big GNU toolchain news (including sourceware news):
 * The GNU tools cauldron was last weekend and it was huge success
  * Videos will be coming soon
 * Toon retired from the GCC steering committee
  * https://inbox.sourceware.org/gcc/cf4368d2-1606-4c53-8579-5e26ef914b38@moene.org/
 * Re-enabling account signup on Bugzilla
  * https://inbox.sourceware.org/gcc/871p9w53w8.fsf@gentoo.org/

GCC easy issue to tackle of the week:
 *  Missed optimization: fold `(a^b) <= 3` to `b < 4` for bool a
  * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115392
  *  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 (2 weeks):
 * https://gcc.gnu.org/r17-4706 ... r17-5074 -  369 commits
 * phiopt: Factor out ~/- with one constant
  * https://gcc.gnu.org/r17-4785-g0ce42336870430
 * Merge common attribute handling code between libgccjit/Rust and c-family.
  * https://gcc.gnu.org/r17-4824-g54df3a3d98b521
  *https://gcc.gnu.org/ r17-4974-gf9db2688e21d37
 * range-op: implement lhs_op[12]_relation for AND, OR, MIN, and MAX
  * https://gcc.gnu.org/r17-4863-g7b3563c38b7b1e
 * VRP: fold a LE or GE test between two names to an equality
  * https://gcc.gnu.org/r17-4864-g3526c3b792cc55
 * i386: Ensure the x86 backend is any-or-plus (AOP) safe.
  * https://gcc.gnu.org/r17-4875-gcc195978102e20
 * aarch64: Port some NEON intrinsics to pragma-based framework
  * https://gcc.gnu.org/r17-4912 https://gcc.gnu.org/r17-4913
  * https://gcc.gnu.org/r17-4914 https://gcc.gnu.org/r17-4915
  * https://gcc.gnu.org/r17-4916 https://gcc.gnu.org/r17-4917
 * some ftrapping-math fixes
  * https://gcc.gnu.org/r17-4920 https://gcc.gnu.org/r17-4921
 * AArch64: Fix PCH PIE builds by using anchor
  * https://gcc.gnu.org/r17-4923-g11a9bf984b1a98
 * missed FRE in loop
  * https://gcc.gnu.org/r17-4840 https://gcc.gnu.org/r17-4886
  * https://gcc.gnu.org/r17-4887
 * c++/modules: P1811: relaxing redefinition restrictions
  * https://gcc.gnu.org/r17-4959-g13920d004da35b
 * bpf: Some indirect call fixes
  * https://gcc.gnu.org/r17-5012 https://gcc.gnu.org/r17-5013
https://gcc.gnu.org/r17-5014
 * configure cleanups
  * https://gcc.gnu.org/r17-5035 ... https://gcc.gnu.org/r17-5040
  * https://gcc.gnu.org/r17-5049 ... https://gcc.gnu.org/r17-5054
  * https://gcc.gnu.org/r17-5073

GCC discussion:
 * default C++ operator new's alignment
  * https://inbox.sourceware.org/gcc/CAH6eHdSDb2YWuUw7tgqowhBd8APuyn4zXDwvWEXz0+3UsKFU3w@mail.gmail.com/T/
 *

GCC bugzilla stats (2 weeks)
  *  202 new issues filed
  *  119 issues closed

 binutils/gdb commits:
 * gdb: Add source-tracking breakpoints feature
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=ccf0f68e72ea0a5628097b980a04e1a8262781df
 * aarch64: mingw: Auto-import implementation (ld)
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=0bb9902441e417fd43836b0b0fe9466080bb7c43
 * BTF support: dumping and basic BFD support
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=8943e377867eac62928441e5236aa9c866d9dd0e
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=071f8a902eb29d29b9306b1425392e9fc73470f3
 * RISC-V: Introduce TLSDESC relaxation.
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=2c4ccb8103d73917d769cf6c35fa8b71424f20ca
 *

gdb discussion:
 *
binutils discussion:
 *
glibc commits:
 * math: Use cbrt from CORE-MATH
  * https://sourceware.org/cgit/glibc/commit/?id=a3205d5afb901888dfeed1333e753259a76aea02
 * AArch64: Add SVE2 strlen
  * https://sourceware.org/cgit/glibc/commit/?id=a70e02421575af5e409c47d7d65eaa1b223f41e4
 *
glibc discussion:
 * Requiring and enforcing known-key gpg commit signatures
  * https://inbox.sourceware.org/libc-alpha/utJRORcFQTyC89QDdyEO6g@gentoo.org/

  reply	other threads:[~2026-10-12  7:24 UTC|newest]

Thread overview: 7+ 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 News Week 56 (September 20, 2026) GNU Tools weekly via Gdb
2026-09-28  7:38       ` GNU Tools Weekly News Week 57 (September 27, 2026) GNU Tools weekly via Gdb
2026-10-12  7:19         ` GNU Tools weekly via Gdb [this message]
2026-10-19  5:59           ` GNU Tools Weekly News Week 60 (October 18, 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=NyP7WhRpthBKDeQ0Mdmm9SuaoeWuDoL7=K6HEG8yAM9Fsg@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