It might be, that we are a little bit to strict with the current call resolving.
We always check the parameter types, also for languages where no function overloading exists.
This will not map function calls, where one of the parameters have an UNKNOWN type.

This is the relevant code part:

Theoretically, for the "not HasFunctionOverloading" case, we could finish here with an ==1:

Or we only take the shortcut, when one of the types is unknown.
Update: Of course, the number of arguments must match, otherwise something is going wrong.
What do you think?

Example where current call resolving fails:

//#define MY_CONST_INT 1

void foo(int i) {
}

int main() {
    foo(MY_CONST_INT);
    return 0;
}