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 42 (June 14, 2026)
Date: Mon, 15 Jun 2026 00:21:50 -0700 [thread overview]
Message-ID: <CAHt=NyNonbJn-qYgZy4UR54x_0g39iMtzGreWj+mp5sM2wJyOg@mail.gmail.com> (raw)
In-Reply-To: <CAHt=NyMQqSikhJAd2inR4X8=D-1pWZwxGJtxwb3GwhfwuuWLvg@mail.gmail.com>
GNU Tools Weekly News Week 42 (June 14, 2026)
Release updates for GNU toolchain:
* GCC 15.3.0 was released
* https://inbox.sourceware.org/gcc/p8nq1983-qn01-7814-3p76-13n5r9q755q2@fhfr.qr/
* GNU binutils 2.46.1 was released
* https://inbox.sourceware.org/binutils/87y0gohcay.fsf@gentoo.org/
GNU toolchain conference reminders:
* FOSSY 2026 toolchain track North America, Aug 6-9 (Vancouver, Canada)
* GNU Tools Cauldron 2026, Fri-Sun, October 2-4 (Prague, Czechia)
* https://gcc.gnu.org/wiki/cauldron2026
* https://conf.gnu-tools-cauldron.org/prg26/cfp
* Toolchains Track at LPC 2026, October 7th (Prague, Czechia)
* https://lpc.events/event/20/abstracts/
General/big GNU toolchain news (including sourceware news):
* Sourceware budget and funding 2026/2027, Fri 12, 15:00 UTC
* notes from the meeting:
https://inbox.sourceware.org/gcc/20260614225910.GA14303@gnu.wildebeest.org/
GCC easy issue to tackle of the week (2 this week):
* `(x == MAX_VALUE) ? y : MIN<x, y>` -> MIN<x,y>
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125700
* Reach out to Andrea Pinski <andrew.pinski@oss.qualcomm.com> for
mentoring on this issue.
* Improve RISC-V sequence for conditional xor with a constant
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125731
* Reach out to Jeff Law <jeffrey.law@oss.qualcomm.com> for
mentoring on this issue.
* Previous ones are listed on https://gcc.gnu.org/wiki/EasyIssuesOfTheWeek
GCC commits:
* https://gcc.gnu.org/r17-1417 - r17-1559 : 143 commits
* aarch64: Add support for FEAT_SSVE_BitPerm and some other intrsinics
* https://gcc.gnu.org/r17-1424-g548b39f569a308 ... r17-1428-g5da2ddf4ef8d94
* aarch64: Use MOVI for low‑64‑bit integer SIMD constant vectors
* https://gcc.gnu.org/r17-1491-gf152cf1734f808
* ranger: Refine modulo range operations with fixed quotient
* https://gcc.gnu.org/r17-1493-gcd52e71e8aea25
* phiopt: Allow factoring out of more than just single operand operations
* https://gcc.gnu.org/r17-1507-gc43fed44d9ac34
* driver: Spill long COLLECT_GCC_OPTIONS to a response file
* https://gcc.gnu.org/r17-1526-g619a5e5586759a
* match: Optimize (~a) >> a to -1 for signed a
* https://gcc.gnu.org/r17-1527-gb3ade4e315e5ba
* match: Add bitop reduction simplifications against zero
* https://gcc.gnu.org/r17-1543-gcee985872c4976
GCC discussion:
*
GCC bugzilla stats
* 138 new issues filed
* 70 issues closed
binutils/gdb commits:
* gdb/MicroBlaze: Add support for native linux gdb:
* https://sourceware.org/cgit/binutils-gdb/commit/?id=d62f64e17b33fb76653fa0c008c61b782d07f8ec
*
gdb discussion:
* RFC: prototype of C extensions using the Python limited API (continued)
* https://inbox.sourceware.org/gdb/21479c1d-3a9a-4ae2-bc1a-5dc19871f275@arm.com/
binutils discussion:
*
glibc commits:
*
glibc discussion:
*
next prev parent reply other threads:[~2026-06-15 7:22 UTC|newest]
Thread overview: 45+ 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 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
2026-04-20 5:10 ` GNU Tools Weekly News Week 34 (April 19, 2026) GNU Tools weekly via Gdb
2026-04-25 23:52 ` GNU Tools Weekly News Week 35 (April 26, 2026) GNU Tools weekly via Gdb
2026-04-25 23:59 ` GNU Tools weekly via Gdb
2026-05-04 1:34 ` GNU Tools Weekly News Week 36 (May 3, 2026) GNU Tools weekly via Gdb
2026-05-06 8:38 ` Jose E. Marchesi via Gdb
2026-05-11 6:15 ` GNU Tools Weekly News Week 37 (May 10, 2026) GNU Tools weekly via Gdb
2026-05-18 9:39 ` GNU Tools Weekly News Week 38 (May 17, 2026) GNU Tools weekly via Gdb
2026-05-25 5:47 ` GNU Tools Weekly News Week 39 (May 24, 2026) GNU Tools weekly via Gdb
2026-05-31 16:39 ` GNU Tools Weekly News Week 40 (May 31, 2026) GNU Tools weekly via Gdb
2026-06-08 20:56 ` GNU Tools Weekly News Week 41 (June 7, 2026) GNU Tools weekly via Gdb
2026-06-15 7:21 ` GNU Tools weekly via Gdb [this message]
2026-06-22 5:21 ` GNU Tools Weekly News Week 43 (June 21, 2026) GNU Tools weekly via Gdb
2026-06-28 21:24 ` GNU Tools Weekly News Week 44 (June 28, 2026) GNU Tools weekly via Gdb
2026-07-05 7:19 ` GNU Tools Weekly News Week 45 (July 5, 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=NyNonbJn-qYgZy4UR54x_0g39iMtzGreWj+mp5sM2wJyOg@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