From: Ian Lance Taylor <iant@google.com>
To: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Replacing certain operations with function calls
Date: Tue, 01 Sep 2009 22:44:00 -0000 [thread overview]
Message-ID: <m3bplul1z3.fsf@google.com> (raw)
In-Reply-To: <c568a2600909011535y109d5c8bv15021125c971f573@mail.gmail.com> (Jean Christophe Beyler's message of "Tue\, 1 Sep 2009 18\:35\:34 -0400")
Jean Christophe Beyler <jean.christophe.beyler@gmail.com> writes:
> 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?
Oh, sorry, I'm an idiot. I forgot that you only have RTL at this point.
I would go with what you wrote and see what happens.
Ian
next prev parent reply other threads:[~2009-09-01 22:44 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
2009-09-01 22:42 ` Jean Christophe Beyler
2009-09-01 22:44 ` Ian Lance Taylor [this message]
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=m3bplul1z3.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=jean.christophe.beyler@gmail.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).