News for hackers. Stuff that matters.

A comment on Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ Bug Took Down Solidity. Parent comment

Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B... by mgaunard on Friday August 15, 2025 @02:28PM (#44915870)
Every new version of C++ (and sometimes even new versions of C++ compilers) can break code in subtle ways.

You should always do extensive testing before upgrading.

[ Parent | on HN ]
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B... by reactordev on Friday August 15, 2025 @02:48PM (#44916108)
That’s the crux of the issue. People fear upgrading because of the bugs introduced by more complexity for more terse syntax.

How much longer will you suffer?

[ Parent | on HN ]
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B... by mgaunard on Friday August 15, 2025 @04:07PM (#44916785)
The same is true for any software. If you care about reliability, you pin, and carefully test before upgrading.
[ Parent | on HN ]
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B... by vlovich123 on Friday August 15, 2025 @06:14PM (#44917886)
I have not observed the same with other languages, whether that’s Java, Rust, or Swift.

And note this is about an older compiler version using an older library with a “newer” language spec (ie been around 5 years). If you use up to date toolchains there’s less of an issue. This is yet another perennial weakness in the c++ ecosystem that isn’t present in other languages because the standard committee continues to abrogate their duties here.

[ Parent | on HN ]