This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problems with sibling calls


Georg-Johann Lay wrote:

> Yes that's right. It would work if I recreate the information which code
> a couple of lines away did already, I just wanted to avoid doubling
> (some parts of) the code/work in order to keep the backend clean.

  Well, then don't!  Factor out the common parts of your stack layout and arg
passing into subroutines that can be called from multiple places in your backend.

> Moreover, calls.c is far from being short and straight forward, and
> obviously many different cases must be handled. Many cases will
> disappear because the implementation is for a specific machine, though.

  You shouldn't need to be doing anything to calls.c itself, unless I've
missed something seriously complicated here.

    cheers,
      DaveK


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]