Target FUNCTION_{PRO,EPI}LOGUE question

[Neil Booth <neil at daikokuya dot demon dot co dot uk>]

I've started putting these functions into our target structure.
However, there is a conflict between "HOST_WIDE_INT" and "int" which
I'm not sure how to resolve.

Most targets, where these macros are implemented as a function, take
the second argument to be an int.  For example:

void
output_arm_prologue (f, frame_size)
     FILE * f;
     int frame_size;
{...}

However, the caller, in final.c, passes get_frame_size() as the second
argument, and get_frame_size() in function.c returns a HOST_WIDE_INT.

My inclination is to stick with an "int" in the function prototype,
rather than a "HOST_WIDE_INT", which seems like overkill.  Is this
correct?

Neil.