When we can't determine with certainty the signature of a function
import we pick the fist one we find rather than error'ing out.
The resulting program might not do what is expected since we might pick
the wrong signature. However since its behaviour in C to use the same
function with different signatures this seems beter than refusing to
compile such programs.
Fixes PR40472
Is there some better way to generate a warning in an llvm pass?