https://bugs.kde.org/show_bug.cgi?id=511972
--- Comment #7 from Sergei Trofimovich <[email protected]> --- (In reply to Paul Floyd from comment #3) > Does that now mean that GCC generates "alloc size larger than" warnings > because it no longer supports > '-Wno-alloc-size-larger-than=18446744073709551615 ? Yeah, the original change resurfaced the warnings again. Your change still keeps it suppressed \o/ (In reply to Paul Floyd from comment #5) > I've changed the -Wno-alloc-size-larger-than=18446744073709551615 options to > -Walloc-size-larger-than=18446744073709551616, which is more than the value > that we are using (usually -1 converted to size_t). Seems to work with clang > 19 and gcc 14. > > commit 51c5973d9d1f096b9472df75638f2a53324fafed (HEAD -> master, > origin/master, origin/HEAD) Works for `gcc-16` as well. No alloc-size related warnings. Thank you! The only new warning in `gcc-16` (unrelated to `-Wno-`) is: new_override.cpp:21:16: warning: variable 'j' set but not used [-Wunused-but-set-variable=] 21 | volatile int j = 0; | ^ An effect of https://gcc.gnu.org/PR44677 ( https://gcc.gnu.org/r16-2258-g0eac9cfee8cb0b21d ). -- You are receiving this mail because: You are watching all bug changes.
