Hmm. SUppressing warning can be a valid thing to do on a blanket basis. The reason being that you can then establish a 'Day zero', after which compilation must be warning free - this will catch any new violations.
Couple this with an ongoing program of steadily removing the old supressions and fixing the underlying code to ensure no wranings are produced, and you can get to where you want to be.
Having 56k warnings can be problematic - where the hell do you start?