6 usability improvements in GCC 15 | Red Hat Developer

https://developers.redhat.com/articles/2025/04/10/6-usability-improvements-gcc-15

#Apple M1 / M2 / M3 Core Support Might Soon Be Merged For The #GCC #Compiler
When it comes to compiler support for #AppleSilicon and their hardware at large, Apple has long been focused on the LLVM/Clang toolchain given their long history with it, employing many of the developers, and Xcode being based on LLVM. The GNU Compiler Collection (GCC) though may soon see upstream support for the newer Apple Cores
https://www.phoronix.com/news/Apple-Cores-GCC-Possibly-Soon

"[…] Let's take a look at 6 improvements to look forward to in the upcoming #GCC 15.

1. Prettier execution paths

2. A new look for C++ template errors

3. Machine-readable diagnostics

4. An easier transition to C23

5. A revamped color scheme

6. libgdiagnostics

We're still fixing bugs, but we hope that GCC 15 will be ready to officially release (as 15.1) sometime later this month. […]"'

https://developers.redhat.com/articles/2025/04/10/6-usability-improvements-gcc-15 – by David Malcolm #gcc15

"the RISC-V port of #GCC was introduced only in GCC 7.5.0—a version that requires C++ and cannot be bootstrapped! To this end, we have been improving MesCC, the C compiler that comes with Mes, so it is able to build GCC 4.6.5; meanwhile, Ekaitz Zarraga backported RISC-V support to GCC 4.6.5, and backported RISC-V support from the latest tcc to our bootstrappable-tcc."

That’s the kind of heroism in #software development that you rarely hear about:
https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down/
https://www.gnu.org/software/mes/

Urge your Congressmember to stand firm against the assaults on our #democracy, the #judiciary & the rule of #law by rejecting the #JUDGES Act, the #PEPPER Act, the #NORRA Act & The #NIAP Act today.
https://resist.bot/petitions/PDVYDP

#ResistBot #resist #coup #Trump #Musk #StephenMiller #Vought #SupremeCourt #SCOTUS #POTUS #TeslaTakedown #FAFO #NAFO #Putin #MBS #Xi #Modi #SaudiArabia #GCC #UAE #Dubai #Oman #Qatar #Bahrain #Kuwait #PetroState #climate #ClimateChange @resistbot @jesscraven101@bsky.social

A new #blog post appears!

I built a native GCC 14.2.0 for Mac OS X 10.4 Tiger PowerPC.

https://briancallahan.net/blog/20250329.html

The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

Should GLibC be built first? Why (or why not)?

[1] https://savannah.nongnu.org/task/?15390
[2] https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718

Now that we've gone through all six #memorabilia, we are re-opening bidding for the #GNU head, the pair of #GCC prints, the GNU Party drawing, and the Norbert Wiener Award for Social and Professional Responsibility on #Galène #auction #FSF40

Today's `gcc` bug is https://gcc.gnu.org/PR119428

There `gcc` generated wrong code for `e2fsprogs-1.47.2` on the code similar to:

void bug_o2(unsigned int nr, unsigned char * addr)
{
unsigned char *ADDR = addr;
ADDR += nr >> 3;
*ADDR &= (unsigned char) ~(1 << (nr & 0x07));
}

It was supposed to set bit `nr` in a bit vector `addr` to 0. But did something else instead.

My first GCC commit!

Although my first C compiler was Borland Turbo C, GCC has always offered a better programming experience. My journey with GCC started in the late '90s, back when Red Hat was a rad startup, The Matrix was blowing minds, and Rage Against the Machine was blasting through boombox.

After decades of using the GCC toolchain, I now find myself contributing to its codebase. Excited to share my first commit to the GCC project, adding a few intrinsic functions to arm_acle.h.

Huge thanks to everyone on the GCC team for their support!

https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f4f7216c56fe2f67c72db5b7c4afa220725f3ed1

Here #MBS openly bribes/pays #Trump / #MusKKK salaries along with their #Republican #DeathCult and somehow the #BrainTrust here in the #USA sells this as us being tough on #SaudiArabia / #GCC / #UAE / #Quatar / #Oman / #Kuwait / #Bahrain
https://expressional.social/@Peter_Link/113979751293895621

Today's `gcc` bug is a https://gcc.gnu.org/PR119278

There `gnutls-3.8.9` test suite triggered `gcc`'s ICE in `-fanalyzer` mode on code that is not supposed to generate any meaningful code.

Some partnerships redefine what’s possible, and our 15-year journey with REA Group is a testament to that. Together, we've tackled complex challenges, built high-performing teams, and driven innovation at scale.

As REA expands in Cyber City, we’re proud to support their vision for a future-ready tech landscape—one powered by autonomy, excellence, and bold thinking: https://ter.li/6fr0l2

Watch the video to see how we’re shaping the future, together.

Today's bug is a `gcc` SIGSEGV: https://gcc.gnu.org/PR119226.

There `gcc` started crashing on certain uses of `strcspn()`. `vifm-0.14` happened to be one example of that.

Healthy Competition With #GCC15 vs. #LLVM #Clang20 Performance On #AMD #Zen5
With some codebases/workloads there can be strong advantages at time for one compiler over the other, but at a high level the #GCC and Clang #compiler performance is extremely tight with recent versions and on modern #x86_64 hardware.
https://www.phoronix.com/review/clang20-gcc15-amd-znver5

“The exact chain of command involved was unclear.”

Meaning: foreign adversaries are the chain of command.

#GCC #Russia #Putin #Trump #Musk #coup #DOGE #Ukraine
https://www.politico.com/news/2025/02/25/state-department-grant-ukraine-aid-waivers-00205989

gotta reward the foreign oligarchs for stealing money from their people so #Trump, #Musk, #Russia, the #GCC, and the other funders can rob us.

@RichardNairn @GottaLaff https://mstdn.ca/@RichardNairn/114068491635772387

Upgrading emacs-plus to 30.1 and getting gcc/libgccjit errors? I did too! But I think I fixed it easily enough: https://github.com/d12frosted/homebrew-emacs-plus/issues/790