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 29 (March 15, 2026)
Date: Sun, 15 Mar 2026 22:33:22 -0700	[thread overview]
Message-ID: <CAHt=NyO6evRk0DbxBHD-QnOpf9RsUri5cMBNDOsVtm_kkTc76w@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyN1HLULR_wFt5NU2N6jw_L8XTrm64PufwhCfVkdFgSaAQ@mail.gmail.com>

GNU Tools Weekly News Week 29 (March 15, 2026)

Release updates for GNU toolchain:
 * GCC 16.0.1 release status:
  * https://inbox.sourceware.org/gcc/6277162s-n588-nps4-551p-nsp885rn4212@fhfr.qr/T/#u
 * gcc 16.0 regression status (note this is not official numbers, it
might be off by a few)
  * P1:                       11            -5
  * P1+P2+P3 total: 776           -17


General/big GNU toolchain news (including sourceware news):
 * Notes from Sourceware Open Office, Fri 16:00 UTC
  * https://inbox.sourceware.org/gcc/20260316011308.GA32479@gnu.wildebeest.org/
 * Dimitar Dimitrov was appointed as PRU binutils maintainer
  * https://inbox.sourceware.org/binutils/fa6e9bc9-60d1-458c-832c-02fbcda99c4e@suse.com/T/#m8dcf81087b993f0b82b392d72427b3e73a4dc920
  * https://sourceware.org/cgit/binutils-gdb/commit/?id=cd764745c794944601d7aa1b836597475f5f0f33

GCC easy issue to tackle of the week:
 * `(x ^ (-CMP)) + CMP` -> `CMP ? -x : x`
  * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113894
  * 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
 * arm: Add support for _BitInt(N)
  * https://gcc.gnu.org/cgit/gcc/commit/?h=trunk&id=e256eb478ad1b8c2c767aa35e03903bf4cd7c842
 * c++: require C++26 for -freflection
  * https://gcc.gnu.org/cgit/gcc/commit/?h=trunk&id=9bb200e71ccf9c923bd9c7bd546130446fd76e95
 * doc: Move specs documentation to GCC internals manual
  * https://gcc.gnu.org/cgit/gcc/commit/?h=trunk&id=c600bb7aefca1ac43e57ac8dde957183a8fca7a9
 *

GCC discussion:
 * GSoC 2026 project discussions from participates
 * Policy on use of LLM tools and bug fixes
  * https://inbox.sourceware.org/gcc/CAFiYyc3XoTbYe_pjpj5PvmiNN2uX58ssjMh4Dr3=euqpP1SruQ@mail.gmail.com/T/#m4365c662ccc0af15fe987fdd87556fb842e62d2a
 * [RFC] Builtins for C++26 integer atomic reductions
  * https://inbox.sourceware.org/gcc/ECACB51F-CEDC-4772-B311-464590D5F340@nvidia.com/T/#m32107687793209cbbaa543c10e139cf381e121ed
 * Questions on PROMOTE_MODE, function_promote_mode
  * https://inbox.sourceware.org/gcc/306d4117-9e41-4732-a1ad-d4d88fdd2218@oss.qualcomm.com/T/#md49ec554ad57e804e4f055ee8ab273d8a2c9a740
 *


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

glibc commits:
 * LoongArch: Optimize float environment functions
  * https://sourceware.org/cgit/glibc/commit/?id=41e2067a8f238310e72e70b21f7d67fe7d8a9189
 * Support loading libunwind (from LLVM compile-rt) instead of libgcc_s
  * https://sourceware.org/cgit/glibc/commit/?id=5d89e7c47cc9d27475e086dedbeecc69be82aa74
 * malloc: Improve memalign alignment
  * https://sourceware.org/cgit/glibc/commit/?id=28882c408c7177ff82277bd69f0d7d4078f72561

glibc discussion:
 * [Question] Will switching Linux UAPI headers from __ASSEMBLY__ to
__ASSEMBLER__ affect glibc?
  * https://inbox.sourceware.org/libc-alpha/CABZAGREvnu7DYOyCEYdjOSPMzhbjexmx55Xi9wjNeXd_CuaUxA@mail.gmail.com/T/#m28911e194ed53e1e0e982815f6d035f9fb73c3c5
 * glibc test time regression after gawk update
  * https://inbox.sourceware.org/libc-alpha/202603091211.629CBP4A089309@freefriends.org/T/#me1cf4fe55daef0968479dcb9db5f971bc6770127
 *
binutils/gdb commits:
 * gdb: boolification
  * Many commits so not listing
 * bfd: boolification
  * Likewise

gdb discussion:
 *

binutils discussion:
 *

  reply	other threads:[~2026-03-16  5:36 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 via Gdb [this message]
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=NyO6evRk0DbxBHD-QnOpf9RsUri5cMBNDOsVtm_kkTc76w@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