[issue40952] GCC overflow warnings (format-overflow, stringop-overflow)

2020-11-06 Thread Nick Coghlan
Nick Coghlan added the comment: I *think* the lnotab one is the compiler failing to detect that the pointer has been updated to point inside the body of a Python object, but I'm also not 100% sure that it's a false alarm. -- nosy: +ncoghlan ___

[issue40952] GCC overflow warnings (format-overflow, stringop-overflow)

2020-06-12 Thread Christian Heimes
New submission from Christian Heimes : I'm getting a couple of compiler warnings with gcc-10.1.1 (Fedora 32) with an asan and ubsan build: Parser/string_parser.c: In function ‘decode_unicode_with_escapes’: Parser/string_parser.c:100:17: warning: null destination pointer [-Wformat-overflow=]