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, gdb@sourceware.org, libc-alpha@sourceware.org,
	 binutils@sourceware.org
Cc: "andrew.pinski@oss.qualcomm.com" <andrew.pinski@oss.qualcomm.com>
Subject: Re: Weekly news letter for GNU toolchain: Week 1 (August 31, 2025)
Date: Wed, 3 Sep 2025 15:39:12 -0700	[thread overview]
Message-ID: <CAHt=NyOKF2eZnQDHpRzdB5nGkmjhVVR5cnHM9R2SMiMBZPV-Ag@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyOAyzyd48TkouKg8o1oMypsE9ADxYL1+mRmieE1WcMamA@mail.gmail.com>

Week 1 (August 31, 2025)
***** Today is the last day to submit proposals and last day to
register to GNU Tools Cauldron 2025 *****

GCC update:
Mailing list update:
* discussion about `Providing more precise "excess errors" message in DejaGnu`
   https://inbox.sourceware.org/gcc/6e61550e-1ce3-48cf-8a1a-fec701a8efcf@gmail.com/T/

Major patches pushed:
* C++ CWG3048 - Empty destructuring expansion statements
* C++: Fix `>` in braced-init-lists and lambdas in template arguments
* C++: Fix `0[a ? x : y]` handling where x and y were arrays
* libstdc++: Implement C++26 <debugging> features
* libstdc++: C++20: Change the value of _Unordered comparison value to
min character value (-128)
** WARNING: ABI breakage; C++20 considered experimental
* memcmp improvement; moves the expansion earlier
* Improve tail recursion for C++ (with exceptions turned on)

GCC bugzilla summary:
* 82 new issues open
* 81 issues have been closed

      reply	other threads:[~2025-09-03 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 22:37 GNU Tools weekly via Gdb
2025-09-03 22:39 ` GNU Tools weekly via Gdb [this message]

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=NyOKF2eZnQDHpRzdB5nGkmjhVVR5cnHM9R2SMiMBZPV-Ag@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