public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Ian Lance Taylor <iant@google.com>, gcc@gcc.gnu.org
Subject: Re: Problems with sibling calls
Date: Fri, 29 May 2009 16:59:00 -0000	[thread overview]
Message-ID: <4A201026.5020605@gmail.com> (raw)
In-Reply-To: <4A201619.3010305@gjlay.de>

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

  reply	other threads:[~2009-05-29 16:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 14:16 Georg-Johann Lay
2009-05-29 16:14 ` Dave Korn
2009-05-29 16:56   ` Georg-Johann Lay
2009-05-29 16:57     ` Dave Korn
2009-05-29 16:26 ` Ian Lance Taylor
2009-05-29 16:38   ` Georg-Johann Lay
2009-05-29 16:59     ` Dave Korn [this message]
2009-05-30 18:26 ` Ulrich Weigand
2009-06-01 14:03   ` Georg-Johann Lay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A201026.5020605@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=avr@gjlay.de \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).