https://bugs.kde.org/show_bug.cgi?id=390524
Ivo Raisr <iv...@ivosh.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |iv...@ivosh.net
Resolution|--- |WONTFIX
--- Comment #3 from Ivo Raisr <iv...@ivosh.net> ---
Support for binary constants has been around since gcc 4.3.0 (since 2008, 10
years ago). Also clang supports this notation. I don't see any reason why we
need to prefer compatibility with ancient compilers over readability and
maintainability.
I think your case is a singular one; majority of LTS distros have moved off of
such ancient gcc versions long time ago. You can't expect recent version of
Valgrind work with an ancient version of the compiler; neither is the case of
other toolchain components.
There are going to be more and more cases of Valgrind using compiler features
available only to reasonably recent compilers. You could get away for now with
a simple patch, changing the binary constants into hexadecimal ones, for
example. But with the evolution bringing new changes, you could end up with a
huge patchset eventually.
--
You are receiving this mail because:
You are watching all bug changes.
