Should static initializer warnings be supressed?

[Christian]

When building Darling, many warnings regarding the use of static initializers are generated. Should something be done to address these warnings, or should they be suppressed with -no_warn_inits? if the warnings can be suppressed, can they be globally suppressed, or should this be addressed on a case by case basis?

Here is a sample warning for reference:

ld: warning: static initializer found in 'src/frameworks/path/to/some/framework/'.

[Ariel Abreu]

I think these should be perfectly safe to ignore (and globally suppress).