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 30 (March 22, 2026)
Date: Mon, 23 Mar 2026 12:40:51 -0700	[thread overview]
Message-ID: <CAHt=NyMe32SEHNGf0A=cfeimQXYzfB1Mxo9crhT0WX9dPnJTAA@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyO6evRk0DbxBHD-QnOpf9RsUri5cMBNDOsVtm_kkTc76w@mail.gmail.com>

GNU Tools Weekly News Week 30 (March 22, 2026)

Release updates for GNU toolchain:
 * gcc 16.0 regression status (note this is not official numbers, it
might be off by a few)
  * P1:                       9            -2
  * P1+P2+P3 total: 773          -3

General/big GNU toolchain news (including sourceware news):
 * Sourceware Survey 2026
  * https://inbox.sourceware.org/gcc/20260320112515.GO344@gnu.wildebeest.org/T/#u
 * GNU toolchan open office hours were held
  * notes can be found at https://gcc.gnu.org/wiki/OfficeHours

GCC easy issue to tackle of the week:
 * Missed optimisation: std::in_range simpler size check
  * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118879
  * Reach out to Andrew Pinski <andrew.pinski@oss.qualcomm.com> for
mentoring on this issue.

GCC commits:
 * note most of the commits from now until the release are bug fixes
which have not been listed here normally
 * libstdc++: Implement [simd] for C++26
   * https://gcc.gnu.org/cgit/gcc/commit/?id=8be0893fd98c9a89bbcd81e0ff8ebae60841d062
 * c++: enable contracts under -std=c++26
  * https://gcc.gnu.org/cgit/gcc/commit/?id=62a3c3d5951d078f165ea2c3dc461109b131a289
 * gccrs: Sync 41 patches

GCC discussion:
 * GSoC 2026 project discussions from participates
 * Policy on use of LLM tools and bug fixes (continued):
  * https://inbox.sourceware.org/gcc/CAFiYyc3XoTbYe_pjpj5PvmiNN2uX58ssjMh4Dr3=euqpP1SruQ@mail.gmail.com/T/#m4365c662ccc0af15fe987fdd87556fb842e62d2a
 * COBOL: Hoping for insight with middle-end computation time.
 * https://inbox.sourceware.org/gcc/CAFiYyc3k3PGmvYr+vRoP0VUN+TsBCm8iZfwUT2YMCrZVk4oRDA@mail.gmail.com/T/#m22a906fc6d95d3702a31a1024f292d7f0d6570e3
 * RFC: Allow "(mem:<vectype> (reg:<vectype>))"
  * https://inbox.sourceware.org/gcc/2d3b73d2-9221-7b98-8fcf-c4fcf2be619c@suse.de/T/#m6a9c799fd3d51a396036c6963fdeffee7fd68705
 * Earliest version of gcc the project should support as stage1 for gcc 17
  * https://inbox.sourceware.org/gcc/BC210281-A856-43EE-A297-984DA40A1AE2@comcast.net/T/#m411c5ed5aec8ad76588372fb333a6a5239402dd4

GCC bugzilla stats
 * 73 new issues filed
 * 129 issues closed

glibc commits:
 * math: Use cosh, sinh, tanh from CORE-MATH
 * x86_64: Add cosh with FMA
  * https://sourceware.org/cgit/glibc/commit/?id=c7a7bfe54e7d7cf6ff21114dacdeeb543c378dc2
 * math: Sync tgammaf, lgammaf with CORE-MATH
 * AArch64: Remove prefer_sve_ifuncs
  * https://sourceware.org/cgit/glibc/commit/?id=057e7c9aa1578964712ed01e9f7e986412d9fe6c
 * math: Fix spurious overflow and missing errno for lgammaf
  * https://sourceware.org/cgit/glibc/commit/?id=19781c22211c6db827eefc240cb6724b5512fc6b

binutils/gdb commits:
 * infcall: Add support for integer literals as reference function parameters
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=883363daadfa6fc4f9221546f448bfa6a87dd447
 * add i386-phoenix, sparc-phoenix, aarch64-phoenix, arm-*-phoenix target to gas
 *

gdb discussion:
 *

binutils discussion:
 *

  reply	other threads:[~2026-03-23 19:41 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 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 via Gdb [this message]
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=NyMe32SEHNGf0A=cfeimQXYzfB1Mxo9crhT0WX9dPnJTAA@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