https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79929
--- Comment #14 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- (In reply to Martin Sebor from comment #13) > That said, it's possible that the warning could be made clearer if it used > some other notation instead of printing very large positive decimal numbers. > I'm not sure that printing hex numbers instead is the right solution though. > The following doesn't seem much clearer to me: > > Warning: ‘__builtin_memset’: specified size 0xfffffffffffffffb exceeds > maximum object size 7fffffffffffffff [-Wstringop-overflow=] It is not my intention to derail the discussion, but hex numbers are much clearer. One immediately sees that 0x7FFFFFFFFFFFFFFF is ULLONG_MAX/2.
