Migrating go binary to a security-oriented go binary #14769
Description
I've recently published a tool to detect integer overflows in Go, since they're silent by default. The setup is (really) easy: compile the toolchain and use the generated go binary instead of the official go binary. Adding this would help detecting a whole new class of bugs for Go targets in OSS-fuzz that are currently mostly undetected, but I have a few questions before working on it.
What would OSS fuzz folks recommend for the migration to happen ? I'm guessing replacing all Go compilers to go-panikint would be a bit abrupt. What are your migrations recommendations ? Thank you!