On Thu, 3 Mar 2005, Kazu Hirata wrote:
> If we want to change fold_builtin to take operands like op0, op1, and
> op2, I would have to change so many things that depend on
> fold_builtin. (Note that the subroutines of fold_builtin also depends
> on fold_builtin in a sense that they need the origin
Kazu Hirata <[EMAIL PROTECTED]> writes:
> It turns out that the CALL_EXPR case of fold_ternary needs the
> original tree like so. (Notice a reference to t.)
...
> If we want to change fold_builtin to take operands like op0, op1, and
> op2, I would have to change so many things that depend on
> fo
Hi,
These days, I am reorganizing fold. One of my goals is to provide a
function like
fold_ternary (code, type, op0, op1, op2)
without taking a tree that would be obtained by
build3 (code, type, op0, op1, op2)
So we need to eliminate a reference to the original tree, that
ie, the result o
