GNU Tools Weekly News Update Week 6  (October 6, 2025)
(week 5 was skipped)
General/big GNU toolchain news (including sourceware news):*
 Last week was the GNU tools 2025 cauldron
** Happy to see many of you there.
** Hope to continue the discussions on the mailing lists and other places.
** Will post and update when the videos and pdfs on cauldron available
** Thanks again to the host (Faculty of Engineering of the University
of Porto) and organizers for a wonderful and productive cauldron
** Hope to see all of you and more next year

* C++ Weekly With Jason Turner posted about how to use GCC's
`-fstack-usage` feature with @compiler_explorer
** https://youtu.be/kXe-YkJ9nBs

GCC discussion:
* Followup from the cauldron about  "bugzilla keyword for beginner
issues to work on" (cross posted to GDB, glibc and binutils)
** Summary: Use "good-first-issue" and maybe a modifier; make sure
there is a mentor available for the issue
** 
https://inbox.sourceware.org/gcc/[email protected]/T/#m99b5395361ece1d1c3f294e2d5b1582e6d11a39b

* Link to the GCC Steering Committee overview on the wiki was posted
** 
https://inbox.sourceware.org/gcc/cagwvnymg9od9adv_6nbpsxds4kymuwngkcczvh3-xw-wxcc...@mail.gmail.com/T/#u
** https://gcc.gnu.org/wiki/gcc-steering-committee

* How to build a cross compiler for NVPTX backend
** 
https://inbox.sourceware.org/gcc/[email protected]/T/#t
** The instructions can be found at
https://gcc.gnu.org/wiki/Offloading#For_Nvidia_PTX:

* `Regarding vectorize pattern recognition for [generic] vector
[extension] code`
** asking how the generic vector extension expansion code works with
respect to shifts with constants as not expanding into a multiply or
an add.
** 
https://inbox.sourceware.org/gcc/[email protected]/T/#me17225d58ef3e998e5897ebd6c9c0bc3b344f49e

GCC commits:
* Removal of the fold_builtin (fab) pass
** Merged functionality into other passes
* Function multi-version (FMV) support was improved to now follow ARM's ACLE
**  This change was done for better support for aarch64 and riscv and
even improves x86_64 support for it
** Support was added to the C front-end also
** AARCH64 support is no longer beta
* libstdc++: Implement Philox Engine, c++26 P2075R6
** First time contributor; https://github.com/1nfocalypse
* Improvements for AutoFDO and profiling in general
* toplevel: unify the GCC and GDB/binutils .editorconfig files
** Should help new developers
* C: Add -Wmultiple-parameter-fwd-decl-lists new warning
* C++: Implement C++26 P2795R5 - Erroneous behavior for uninitialized reads
* Ada: Availability of the Extended_Access aspect.
** Helps the interfacing of Ada with other langages with respect to
memory allocation of unconstrained arrays
** https://gcc.gnu.org/onlinedocs/gnat_rm/Aspect-Extended_005fAccess.html


GCC bugzilla stats (includes previous week too):
* 149 new issues filed
* 113 issues closed

glibc commits:
* C23: Implement memset_explicit
* AArch64: Implement AdvSIMD and SVE log2p1(f) and log10p1(f) routines
* C23: Add once_flag, ONCE_FLAG_INIT and call_once to stdlib.h
* Optimize flt-32 and dbl-64 remainder implementation

glibc discussions:
* Banning LLM-generated or assisted contributions to the GNU C Library
** 
https://inbox.sourceware.org/libc-alpha/[email protected]/T/#m150c261c0efeec12da4b0b193ba79f45ddbb9d37
** Note there is a related binutils discussion (see below)

gdb/binutils commits:
* aarch64: Update and fix some of the system registers for
assembler/disassembler
* Add the ability to find the clang LTO plugin to use automatically
with ar/ld/ranlib.
* Many gdb cleanups

binutils discussion:
* RFC: The Binutils and LLM generated patches
** 
https://inbox.sourceware.org/binutils/[email protected]/T/#mb0cdf5c6e1a626a19a1470137e5a731058064cce
** See the related glibc discussion above (there is cross over between
the 2 discussions)

gdb discussion:
* gdb does not stop at printf for ppc
** 
https://inbox.sourceware.org/gdb/[email protected]/T/#m6b827501a18f4b1006fcfe390815e818107a1c47
** gdb and libc issue combined and how display/handle function alias
via GCC asm extension

Reply via email to