On Wed, Jan 6, 2010 at 2:13 PM, Paulo J. Matos <pocmatos@xxxxxxxxx> wrote: > > 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? > Well, just found I can't. From the internals on TARGET_FUNCTION_OK_FOR_SIBCALL: "The hook is used to enforce these restrictions, as the sibcall md pattern can not fail, or fall over to a “normal” call." > 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 > -- Paulo Jorge Matos - pocmatos at gmail.com http://www.pmatos.net
