public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Difference between {expand,fold,simplify}_builtin_foo ???
Date: Mon, 20 Sep 2004 20:04:00 -0000	[thread overview]
Message-ID: <200409201845.i8KIjdTK020464@caip.rutgers.edu> (raw)
In-Reply-To: <1095702500.10950.60.camel@localhost.localdomain>


 > The key difference between them is the simplify_ variant is not
 > allowed to generate RTL nor create non-gimple code.
 > jeff

Ok thanks, that explains expand_builtin_* vs. simplify_builtin_*.

However what about fold_builtin_*?  Both fold_builin_* and
simplify_builtin_* return trees.  Are the fold_ variants allowed to
produce non-gimple?  Or are fold_builtin_* and simplify_builtin_*
really the same and we should canonicalize the naming convention?

If so, which is preferred?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu

  reply	other threads:[~2004-09-20 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 18:29 Kaveh R. Ghazi
2004-09-20 18:38 ` Eric Christopher
2004-09-20 19:51   ` Kaveh R. Ghazi
2004-09-22  6:04     ` Eric Christopher
2004-09-22 17:34       ` Richard Henderson
2004-09-20 18:45 ` Jeffrey A Law
2004-09-20 20:04   ` Kaveh R. Ghazi [this message]
2004-09-21  7:53     ` Jeffrey A Law
2004-09-22  9:38       ` Roger Sayle

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=200409201845.i8KIjdTK020464@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.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).