On Wed, Jan 6, 2010 at 11:36 AM, Paulo J. Matos <pocmatos@xxxxxxxxx> wrote: > By reading the code for i386 it seems that the solution is to have a > single function that expands the epilogue whose argument indicates if > this should be a sibcall or not and depending on the argument perform > the right actions. (corresponding to the ix_expand_epilogue of i386) > :-) > An issue arose during the implementation of the solution to my initial problem. As far as I understood epilogues include a return instruction but not sibcall epilogues. Therefore, if decide to do sibcall from TARGET_FUNCTION_OK_FOR_SIBCALL and later in the expand_epilogue, I decide that I don't want to do a sibcall, I need to somehow avoid the generation of the sibcall return outside the epilogue (usually done through sibcall, sibcall_value, etc.). How can I do this? Cheers, Paulo Matos > Thanks, > > -- > Paulo Jorge Matos - pocmatos at gmail.com > http://www.pmatos.net > -- Paulo Jorge Matos - pocmatos at gmail.com http://www.pmatos.net
