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 8 (October 19, 2025)
Date: Mon, 20 Oct 2025 00:58:15 -0700	[thread overview]
Message-ID: <CAHt=NyO8g64b7LBuAOUM2m5E_ruuKV8osytFvseDUz--XaHNjA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyNXXPShoxuBUdL5zK_XMU4tkjnuf00C_3Sgor9pOQEiVA@mail.gmail.com>

GNU Tools Weekly News Update Week 8  (October 19, 2025)

General/big GNU toolchain news (including sourceware news):
* notes from Sourceware Open Office was held on Friday October 10th
** https://inbox.sourceware.org/gcc/20251016235632.GR30855@gnu.wildebeest.org/

GCC discussion:
* New GCC maintainers/reviews
** Tamar Christina is co-maintainer of the vectorizer
*** https://inbox.sourceware.org/gcc/CAGWvnyngWFgCRASRvTe2PoH4r8+A5WZGeChi1U+CW69hOOF2Mw@mail.gmail.com/T/#u
** Robin Dapp is a reviewer of the vectorizer
*** https://inbox.sourceware.org/gcc/CAGWvnyn8WuNoJ_Q8Mh_k7J=2QU0sRHs3FqoBJoWaSmccqU+zvg@mail.gmail.com/T/#u
** tree-if-conv.cc is officially part of the vectorizer maintainership area
*** https://inbox.sourceware.org/gcc/CAGWvnymXW5yWq_JT3mF=ea2PRPRDtRg6jj7u_Nr=g-otBDfe_w@mail.gmail.com/T/#u
* Patches for adding Algol 68 to GCC were posted
** https://inbox.sourceware.org/gcc-patches/87ms5magbr.fsf@gentoo.org/T/#t
* How to write/read tree contains ssa_name in lto
** https://inbox.sourceware.org/gcc/CAPt2h2bGo-cHK8CGc6=s2DFjGJwkpPqumT8-VyUZxg8GWVDrAw@mail.gmail.com/
** Turned into a discussion on how to handle recording if 2 memory
allocations happen how to mark if one is loaded from; the other does
not trap too
* plans for gcobol 16
** https://inbox.sourceware.org/gcc/20251006145028.d25a3b8e792fe04512ce3775@schemamania.org/
* Discussion around patches from the sourceware forge
** https://inbox.sourceware.org/gcc/CAPS5khb1AJW3ds-KmDKwBAfWH6ApV-zo-xJoidMPmMxn-kf0vQ@mail.gmail.com/T/#m86a67388fed189739518ee1314f3e8736bbf0833
* Add btf_decl_tag and btf_type_tag C attributes for GCC v11 of the patches
** https://inbox.sourceware.org/gcc-patches/20250927090702.979562-1-david.faust@oracle.com/T/#m0812b326872ebae48b935274726e5ec1f1a18b46

GCC commits:
* Enable constant propagation to OpenMP kernels
** New first time contributor
** big improvement for openmp
* Allow target to chose address-space for artificial rodata
** Improves AVR target size requirements when dealing with conversion
of switch tables to constant lookup tables and CRC lookup tables
** https://gcc.gnu.org/cgit/gcc/commit/?h=trunk&id=e347e2b81ac7daa7382c611a62d54ec0b761bee8
** 7 years from the initial patch to the current pushed one
* Initial support for Intel Wildcat Lake processors
* Implement P1494 and P3641 Partial program correctness (c++ and library)
* Enable runtime thread detection with -ftree-parallelize-loops
* libstdc++: Implement P2835R7 Expose std::atomic_ref's object address

GCC bugzilla stats
 * 77 new issues filed
 * 60 issues closed

 glibc commits:
* Implement C23 memalignment
* aarch64: clear ZA state of SME before clone and clone3 syscalls

glibc discussion:
* compiling with clang patches posted
** https://inbox.sourceware.org/libc-alpha/20251017191632.2278298-1-adhemerval.zanella@linaro.org/

gdb/binutils commits:
* binutils: Add a position statement about LLM generated content
** https://sourceware.org/cgit/binutils-gdb/commit/?id=c0316a54b489d68e30de718aee69ab441799aad2

 binutils discussion:
* continued GNU Tools Cauldron SFrame talk notes
** https://inbox.sourceware.org/binutils/933bbc83-5732-4655-870c-4c50b3742637@oracle.com/
** Also related LLVM discussion about adding SFrame support:
https://discourse.llvm.org/t/rfc-adding-sframe-support-to-llvm/86900

  reply	other threads:[~2025-10-20  7:59 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 via Gdb [this message]
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

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=NyO8g64b7LBuAOUM2m5E_ruuKV8osytFvseDUz--XaHNjA@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