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: Re: GNU Tools Weekly News Week 11 (November 9, 2025)
Date: Thu, 13 Nov 2025 16:43:03 -0800 [thread overview]
Message-ID: <CAHt=NyPntsf9FjtMa2p+vFEDPMkq62J5R4fzK7+qbSDtPUNR_Q@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyPaAZhqc3WSi1_WMBr=uZmZL=Jc2jwgQibeR1n6xwqyKA@mail.gmail.com>
Sorry for being late (stuff happened)
GNU Tools Weekly News Week 11 (November 9, 2025)
General/big GNU toolchain news (including sourceware news):
* GCC stage 1 ends Nov 14th this week!
* new gprofng maintainers in binutils
** Claudiu Zissulescu and Jose E. Marchesi, congrats
* The GCC Steering Committee has a wiki page detailing their mission
and current requests are listed
** https://gcc.gnu.org/wiki/gcc-steering-committee
* GCC (GNU Toolchain) dev room at FOSDEM 2026, January 31-Februrary
1, Brussels, Belgium - Calls for proposals
** https://inbox.sourceware.org/gcc/875xparmhn.fsf@kataplop.net/
* Updated Getting started page on the GCC wiki (GCC 101)
** https://gcc.gnu.org/wiki/GCC101
** Base tutorial started and hope others can add to it for the 200 series
** Other projects in the toolchain should have a similar page too
GCC discussion:
* Question about conditional functional unit reservation
* https://inbox.sourceware.org/gcc/aQvprPLNQTDvdcGK@dalaran/
* Change the default C++ dialect to gnu++20?
* https://inbox.sourceware.org/gcc/aQj1tKzhftT9GUF4@redhat.com/
GCC commits:
* SSA immediate use iterator checking
** New checking for FOR_EACH_IMM_USE_STMT
* c: GNU extension allowing compound literals of variable size
* RISC-V: Fix the ABI of empty unions and zero length array in struct
* Ada/GNAT 30 patch sync
GCC bugzilla stats
* 106 new issues filed
* 106 issues closed
glibc commits:
* AArch64: Fix instability in AdvSIMD sinh/tan
* Add C23 long_double_t, _FloatN_t
* Support assert as a variadic macro for C23
glibc discussion:
* C23 addition of once_flag to <stdlib.h>
** https://inbox.sourceware.org/libc-alpha/CAH6eHdT65txghU9_eF+zWykTt86o__4pwJsA0PC8kkM2aDcs5A@mail.gmail.com/T/#m233b3244f2981dffb81772f99a90fab9137d5d01
binutils/gdb commits:
* new gprofng maintainers
next prev parent reply other threads:[~2025-11-14 0:49 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 via Gdb [this message]
2025-11-14 0:51 ` GNU Tools Weekly News Week 11 (November 9, 2025) 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=NyPntsf9FjtMa2p+vFEDPMkq62J5R4fzK7+qbSDtPUNR_Q@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