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 21 (January 18, 2026)
Date: Mon, 19 Jan 2026 00:46:04 -0800	[thread overview]
Message-ID: <CAHt=NyNUyUiehSd4ZvQuFGrRm2X4vUBmUssA-+FpfPvey2vnKA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyOACt0uHs3a0XEGf9_saq_MkW_XQw=uegOtPUPm6t8qYg@mail.gmail.com>

GNU Tools Weekly News Week 21 (January 18, 2026)

Release updates for GNU toolchain:
 * GCC 16.1.0 release status, stage 4 is now in effect
  * https://inbox.sourceware.org/gcc/8rq8os16-o468-p284-11nr-6pn9q0rnrqon@fhfr.qr/T/#u
 * binutils 2.46 release branch is delay until next weekend
  * https://inbox.sourceware.org/binutils/0a2364be-009d-4cb4-ad0e-79c0bc4e195a@oracle.com/T/#ma153c37b55becb027585f2a27a78782d7f81d758

General/big GNU toolchain news (including sourceware news):
 * gccrs December 2025 Monthly report
  * https://inbox.sourceware.org/gcc/34c623b8-6c0d-41c9-921a-613527a64e09@embecosm.com/T/#u
 * GNU toolchain office hours (Asia and Americas/Europe) was held last Thursday
  * Notes can be found at https://gcc.gnu.org/wiki/OfficeHours
 * Sourceware infrastructure updates for Q4 2025
  * https://inbox.sourceware.org/gcc/20260113001906.GM7119@gnu.wildebeest.org/T/#u

GCC commits:
 * gccrs: 22 patch sync
 * c++: C++26 Reflection
 * lto: toplevel inline-asm fixes/improvements
 *

GCC discussion:
 * fate of libxml2 in gcc
  * https://inbox.sourceware.org/gcc/d568aa1c-ddb7-4899-a1c7-fe9d0a088654@debian.org/T/#mbcb36fb29a1728ece2ebada48afe06b650cc3a59
 *

GCC bugzilla stats
 * 141 new issues filed
 * 120 issues closed

glibc commits:
 * Fixes for CVE-2026-0915 and CVE-2026-0861
 * math: Sync acosh, atanh, and asinh from CORE-MATH

binutils/gdb commits:
 * Sframev3 support for binutils
 * aarch64: Add support for FEAT_CMH
 * aarch64: Add support for MLBI system instructions
 * aarch64: Add support for FEAT_MTETC
 * gdb/dwarf: remove support for DWP v1
 *

  reply	other threads:[~2026-01-19  8:48 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 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 via Gdb [this message]
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=NyNUyUiehSd4ZvQuFGrRm2X4vUBmUssA-+FpfPvey2vnKA@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