From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Brooks Moses <brooks.moses@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: RFC: gfc_simplify_transfer implementation.
Date: Wed, 28 Mar 2007 06:16:00 -0000 [thread overview]
Message-ID: <4609F323.40207@lu.unisi.ch> (raw)
In-Reply-To: <4609A592.9080206@codesourcery.com>
Brooks Moses wrote:
> I definitely agree that this sort
> of thing should be pushed off to the middle-end as much as possible.
There are native_encode and native_interpret functions in fold-const.c
(they do require creating trees, of course).
Paolo
next prev parent reply other threads:[~2007-03-28 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 21:53 Brooks Moses
2007-03-27 22:05 ` FX Coudert
2007-03-27 22:16 ` François-Xavier Coudert
2007-03-27 23:39 ` Brooks Moses
2007-03-28 6:16 ` Paolo Bonzini [this message]
2007-03-28 17:52 ` Richard Henderson
[not found] <339c37f20703280927v6fa04329u38088e0d918712e@mail.gmail.com>
[not found] ` <19c433eb0703280947y10fa6d6bs6b1597bd66af2cc4@mail.gmail.com>
2007-03-28 18:38 ` Brooks Moses
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=4609F323.40207@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=bonzini@gnu.org \
--cc=brooks.moses@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).