This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[committed] Fix comment to operand_equal_p
- From: Paolo Bonzini <paolo dot bonzini at polimi dot it>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 15 Jun 2004 12:30:34 +0200
- Subject: [committed] Fix comment to operand_equal_p
This patch updates a comment to operand_equal_p.
Commited as obvious.
Paolo
2004-06-15 Paolo Bonzini <bonzini@gnu.org>
* fold-const.c (operand_equal_p): Fix comment.
*** gcc-save/gcc/fold-const.c 2004-05-28 20:30:47.000000000 +0200
--- gcc/gcc/fold-const.c 2004-06-06 13:40:59.000000000 +0200
***************
*** 2334,2343 ****
executed between the evaluation of its "operands" (which may often
be evaluated in arbitrary order). Hence if the operands themselves
don't side-effect, the VAR_DECLs, PARM_DECLs etc... must hold the
! same value in each operand/subexpression. Hence a zero value for
! ONLY_CONST assumes isochronic (or instantaneous) tree equivalence.
! If comparing arbitrary expression trees, such as from different
! statements, ONLY_CONST must usually be nonzero.
If OEP_PURE_SAME is set, then pure functions with identical arguments
are considered the same. It is used when the caller has other ways
--- 2334,2343 ----
executed between the evaluation of its "operands" (which may often
be evaluated in arbitrary order). Hence if the operands themselves
don't side-effect, the VAR_DECLs, PARM_DECLs etc... must hold the
! same value in each operand/subexpression. Hence leaving OEP_ONLY_CONST
! unset means assuming isochronic (or instantaneous) tree equivalence.
! Unless comparing arbitrary expression trees, such as from different
! statements, this flag can usually be left unset.
If OEP_PURE_SAME is set, then pure functions with identical arguments
are considered the same. It is used when the caller has other ways