In reply to @spotlightkid "Then look at the": looking at the compile time
output I do notice quite a a lot of warnings on multiple topics ".... size 0
overflows the destination" and also mention "<very big value here>08 is bigger
than allowed value ....07" and such, it leaves me to think either the compiler
corrects for this or there are potentially some  vulnerabilities in the compiler

warning: ‘memcmp’ specified bound [9223372036854775808, 0] exceeds maximum
object size 9223372036854775807 [-Wstringop-overread]