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 17 (December 21, 2025)
Date: Mon, 22 Dec 2025 00:51:36 -0800	[thread overview]
Message-ID: <CAHt=NyPC4okeNg3HX3DWM4eV5Q8SJ7tV2Vzj===QftzBhTOupQ@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyPM=1hX72U+3cShS55bTzaGHg_sXcO1yONOVqanC_NsvQ@mail.gmail.com>

GNU Tools Weekly News Week 17 (December 21, 2025)

Release updates for GNU toolchain:
 * GDB 17.1 was released
  ** https://inbox.sourceware.org/gdb/announce.20251220053009.F3797804ED@takamaka.gnat.com/T/#u
 * newlib: Holidays and Yearly Snapshot (news)
  * https://inbox.sourceware.org/newlib/CAOox84srVz_qVyFgSq0r1C=U9KmbOpB6qJ+c2wLke=tcxZzpAg@mail.gmail.com/T/

General/big GNU toolchain news (including sourceware news):
 * ProPolice (SSP [stack protector]) history and integration story into GCC
  * http://miod.online.fr/software/openbsd/stories/propolice.html
 *  Blog posting about Rust GCC backend - Why and how.
   * https://blog.guillaume-gomez.fr/articles/2025-12-15+Rust+GCC+backend%3A+Why+and+how
 * GCC RTL, GIMPLE & MD syntax highlighting for VSCode (forgot about
this last week sorry about that)
  * https://www.reddit.com/r/Compilers/comments/1phcueo/gcc_rtl_gimple_md_syntax_highlighting_for_vscode/
 * Both GNU toolchain office hours happened last week
  * Notes from both meetings can be found at
https://gcc.gnu.org/wiki/OfficeHours
 * FOSDEM 2026: GCC (GNU Toolchain) dev room schedule was posted
  * https://fosdem.org/2026/schedule/track/gcc-gnu-toolchain/
 * GNU toolchain related talks at LPC (Linux Plumbers Conference):
   * GCC BPF:  https://www.youtube.com/watch?v=BHhECeeg87k
   * Adding C library wrappers for all Linux syscalls (glibc):
https://www.youtube.com/watch?v=BPfITyxs0w
 * More Forge, More Actions, More Infrastructure
  * https://inbox.sourceware.org/gcc/20251222022445.GC8131@gnu.wildebeest.org/T/

GCC commits:
 * analyzer: reimplement supergraph to eliminate function_point and
stmt_finder (missed from last week)
 * vect: allow the vectorizer to handle uncounted loops
   * This is mostly used in connection with early break
 * aarch64: Add cortex-a320 core
 * Generate Algol68 frontend online docs
 * aarch64: Add support for memetag-stack sanitizer using MTE insns
 * libstdc++: Implement P2408R5 C++20 iterators as inputs to STL algos
 * x86: Add AMD znver6 processor support
 * GCCrs: 13 patch sync
 * aarch64: Add new target options for 2024 Architecture Extension and Armv9.6-A
 * configure: Support disabling specific languages

GCC discussion:
 * Regarding current state of graphite in GCC
  * https://inbox.sourceware.org/gcc/907df38903e26fcc5d18dcd591a81f7768a1ce26.camel@linux.ibm.com/T/
 * Requiring a BZ account as part of commit access process (continued)
  * https://inbox.sourceware.org/gcc/2fe70219-52ae-4fca-b741-3a20fe062b95@redhat.com/T/#m4b6151ac29053d8c06e1b06bc605005b06721678

GCC bugzilla stats
 * 126 new issues filed
 * 84 issues closed

glibc commits:
 * Deprecate s390-linux-gnu (31bit)
 * malloc: Remove fastbin

binutils/gdb commits:
 * aarch64: Add support for new BTI <target> "r"

  reply	other threads:[~2025-12-22  8:52 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 via Gdb [this message]
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

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=NyPC4okeNg3HX3DWM4eV5Q8SJ7tV2Vzj===QftzBhTOupQ@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