From: Jeffrey A Law <law@redhat.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Difference between {expand,fold,simplify}_builtin_foo ???
Date: Mon, 20 Sep 2004 18:45:00 -0000 [thread overview]
Message-ID: <1095702500.10950.60.camel@localhost.localdomain> (raw)
In-Reply-To: <200409201741.i8KHfi9u009853@caip.rutgers.edu>
On Mon, 2004-09-20 at 11:41, Kaveh R. Ghazi wrote:
> I've been out of GCC most of the summer, so I don't know if this was
> discussed or not. I was wondering what's the reason for and
> difference between {expand,fold,simplify}_builtin_foo().
>
> Looking at e.g. expand_builtin_sprintf and simplify_builtin_sprintf,
> they seem to do exactly the same transformations. Can we just have
> expand_builtin_sprintf call simplify_builtin_sprintf and then expand
> the result? This would remove lots of code duplication and potential
> locations of errors.
I thought that had already been done where possible.
The key difference between them is the simplify_ variant is not
allowed to generate RTL nor create non-gimple code.
jeff
next prev parent reply other threads:[~2004-09-20 17:48 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 [this message]
2004-09-20 20:04 ` Kaveh R. Ghazi
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=1095702500.10950.60.camel@localhost.localdomain \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).