As the subject says, these four standard names are not documented. By analogy to the way in which "sibcall_epilogue" has a separate entry from "epilogue", they should also have their own entries in the "standard pattern names for generation" chapter of the internals manual. The entry for FUNCTION_OK_FOR_SIBCALL even refers to "the 'sibcall' md pattern", but there is no other mention of it.
Note also that if you implement siball_epilogue by emitting a fully-schedulable RTL epilogue (rather than just using an unspec to represent the entire thing as a black box to the compiler and emitting it opencoded at assembler output generation time like the arm port does in 3.3.3 where I discovered this), you may also need to implement these sibcall patterns, or you can get ICEn when the register allocator gets confused in one of the later passes. This dependency is not mentioned anywhere. However I have not tested it against 4.x/HEAD to see if it remains the case.
Interesting, sibcall_epilogue is documented though.
Note I would like these standard names documented also since I would need them to implement them on the SPU (SPE on the Cell) target.
Added by rth's sibcall optimisations back in March 2000:
Should we give him a ping?
Almost four years have gone and nobody was able to document these. It would be nice to see these in the docs! :-)
I am looking for them since I don't know what they are for at the moment, otherwise I could give it a go and contribute!