Too bad with the name clash, but a Pike-prefixed name would also be quite annoying due to its length.
Do you mean that my latest changes introduced the gcc overflow issues or only that you noticed them as of now? I'm also concerned about the overflow detection method using costly integer division on every Pike variable adjustment (machine-code excepted) so if we can optimize that it would be great. Here's a link that I found that could be useful:
https://www.securecoding.cert.org/confluence/display/seccode/INT32-C.+Ensure...