From: Paolo Bonzini Date: Tue, 15 Jun 2004 10:27:30 +0000 (+0000) Subject: fold-const.c (operand_equal_p): Update comment. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=3dd8069d498c0cef2040ea3ce54b793280dfb1a6;p=gcc.git fold-const.c (operand_equal_p): Update comment. 2004-06-15 Paolo Bonzini * fold-const.c (operand_equal_p): Update comment. From-SVN: r83173 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e6038259986..d2c7c64e254 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2004-06-15 Paolo Bonzini + + * fold-const.c (operand_equal_p): Update comment. + 2004-06-15 Kazuhiro Inaoka * config/m32r/m32r.h (RETURN_ADDR_RTX): Define. diff --git a/gcc/fold-const.c b/gcc/fold-const.c index 1cc2b8189c8..3c5a81d7253 100644 --- a/gcc/fold-const.c +++ b/gcc/fold-const.c @@ -2337,10 +2337,10 @@ truth_value_p (enum tree_code code) 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. + 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