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 23 (February 1, 2026)
Date: Mon, 2 Feb 2026 02:19:37 -0800	[thread overview]
Message-ID: <CAHt=NyP07x=0qgHDP9Fx7Uwix_ZW3=94yGUTuJShNE8NAAE=kA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyPh7WCXgNAoi+Cb+Ae+vEqc_tVZ3KJDUEiD7osid-OZvA@mail.gmail.com>

GNU Tools Weekly News Week 23 (February 1, 2026)

Release updates for GNU toolchain:

General/big GNU toolchain news (including sourceware news):
 * FOSDEM was held Saturday/Sunday
  * https://www.fosdem.org/2026/schedule/track/gcc-gnu-toolchain/
  * videos are located in https://video.fosdem.org/2026/ud6215/
 * glibc transition away from sourceware to CTI hosting site (Linux Foundation)
  * https://inbox.sourceware.org/libc-alpha/aXza11xOt8WablUA@arm.com/T/#me3690e18d4836c08c6e24cd1c03956ecab2ee062

GCC commits:
 * note most of the commits from now until the release are bug fixes
which have not been listed here normally
 * c++, contracts: C++26 base implementation as per P2900R14.
 * c++: Implement part of CWG3044
 * C/C++: Better notification if misused a function like macro (e.g.
using assert with the wrong number of arguments)
 * libstdc++/regex: Make DFS executor non-recursive

GCC discussion:
 * Does GCC record optimization information into binary file?
  * https://inbox.sourceware.org/gcc/AFC6461E-C878-45E4-B71A-405E21B74599@oracle.com/T/#m59e008b774df18ee4c860408b2efdca0bc0fb5d6

GCC bugzilla stats
 * 101 new issues filed
 * 96 issues closed

glibc commits:
 *

binutils/gdb commits:
 *

gdb discussion:
 * gdb support for SME-without-SVE ?
  * https://inbox.sourceware.org/gdb/CANnS9rtKj5oDZQ6YuB=rP6YGuC38Gff=TckhDqwaof=A+ot4=w@mail.gmail.com/T/#md7ff6ac528c3b698f3239766eed29f902cc374e1
 *

binutils discussion:
 * More compact SFrames through deduplication
  * https://inbox.sourceware.org/binutils/20260126111821.714eccd1@gandalf.local.home/T/#m6f74937a28ccc58a4c4887092479f089d4126851

  reply	other threads:[~2026-02-02 10:20 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 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 via Gdb [this message]
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=NyP07x=0qgHDP9Fx7Uwix_ZW3=94yGUTuJShNE8NAAE=kA@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