From: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Replacing certain operations with function calls
Date: Tue, 01 Sep 2009 22:35:00 -0000 [thread overview]
Message-ID: <c568a2600909011535y109d5c8bv15021125c971f573@mail.gmail.com> (raw)
In-Reply-To: <m3k50il2sy.fsf@google.com>
I don't think I quite understand what you're meaning. I want to use
the standard ABI, basically I want to transform certain operations
into function calls.
In regard to what you said, do you mean I should build the tree before
the expand pass, by writing a new pass that will work on the trees
instead of rtx?
Otherwise, I fail to see how that is different to what I'm already
doing. Would you have an example?
Thanks,
Jc
PS: Although when I look at what GCC generates at the expand stage, it
really does seem that he first generates the calculation of the
parameters in pseudo-registers and then moves them to the actual
output registers. It's the next phases that will combine the two to
save a move.
On Tue, Sep 1, 2009 at 6:26 PM, Ian Lance Taylor<iant@google.com> wrote:
> Jean Christophe Beyler <jean.christophe.beyler@gmail.com> writes:
>
>> First off: does this seem correct?
>
> Awkward though it is, it may be more reliable to build a small tree here
> and pass it to expand_call. This assumes that you want to use the
> standard ABI when calling this function.
>
> Then your second issue would go away.
>
> Ian
>
next prev parent reply other threads:[~2009-09-01 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 14:27 Jean Christophe Beyler
2009-09-01 16:35 ` Ian Lance Taylor
2009-09-01 18:31 ` Jean Christophe Beyler
2009-09-01 22:20 ` Jean Christophe Beyler
2009-09-01 22:26 ` Ian Lance Taylor
2009-09-01 22:35 ` Jean Christophe Beyler [this message]
2009-09-01 22:42 ` Jean Christophe Beyler
2009-09-01 22:44 ` Ian Lance Taylor
2009-09-02 15:34 ` Richard Henderson
2009-09-02 19:38 ` Jean Christophe Beyler
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=c568a2600909011535y109d5c8bv15021125c971f573@mail.gmail.com \
--to=jean.christophe.beyler@gmail.com \
--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).