Kai Tietz wrote: >> Kai, why is your change making OUTGOING_REG_PARM_STACK_SPACE accept a >> FUNCTION_DECL, rather than a FUNCTION_TYPE? I'd think that all >> calling-convention predicates ought to be looking at the type to support >> calling through function pointers? > > This macro is used also in builtin's and libcalls subject where the > FUNC_DECL is a null reference. Also in most places the FUNC_DECL is > allready present. To avoid duplicate code to check and get the FUNC_TYPE > by FUNC_DECL, I choose to pass the function declaration.
I'm sorry -- that doesn't really answer the question I was trying to ask. To be clear, if we're calling through a function pointer, we still need to be able to do the right thing, and in that case we don't have a FUNCTION_DECL. So, I don't understand how you can have a macro to control the calling convention that accepts a FUNCTION_DECL; I would think it would have to accept a FUNCTION_TYPE. Thanks, -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
