This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/78973] [7 Regression] warning: ‘memcpy’: specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 03 Jan 2017 16:03:29 +0000
- Subject: [Bug c/78973] [7 Regression] warning: ‘memcpy’: specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
- Auto-submitted: auto-generated
- References: <bug-78973-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78973
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2017-01-03
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
I agree that huge decimal numbers can be hard to read (not just in this message
but in all others that print them). I have been thinking about an enhancement
to the pretty printer that would make it possible to use symbolic constants
like INT_MAX or use simple expressions involving them like CHAR_MAX + 2. Using
hexadecimal for very large numbers might be worth considering as well.
That said, unless this particular instance of the warning is a false positive,
I would view this report as an enhancement request rather than a regression.
Can you explain why you marked it as such?