From: Richard Kenner <kenner@gcc.gnu.org>
Date: Mon, 21 Apr 2003 22:39:26 +0000 (-0400)
Subject: Refine last change.
X-Git-Tag: releases/gcc-3.4.0~7108
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4f0baa737f2e56b78f81f07efb9c2a55111edfe3;p=thirdparty%2Fgcc.git

Refine last change.

From-SVN: r65915
---

diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 33057c3b7a84..8368b49f39c6 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -725,10 +725,21 @@ Stored in the @code{integrated} field and printed as @samp{/i}.
 @item RTX_UNCHANGING_P (@var{x})
 Nonzero in a @code{reg}, @code{mem}, or @code{concat} if the register or
 memory is set at most once, anywhere.  This does not mean that it is
-function invariant.  This flag is used to determine whether two
-references conflict.  See @code{tree_dependence} in @file{alias.c} for
-more details.  Stored in the @code{unchanging} field and printed as
-@samp{/u}.
+function invariant.
+
+GCC uses this flag to determine whether two references conflict.  As
+implemented by @code{true_dependence} in @file{alias.c} for memory
+references, unchanging memory can't conflict with non-unchanging memory;
+a non-unchanging read can conflict with a non-unchanging write; an
+unchanging read can conflict with an unchanging write (since there may
+be a single store to this address to initialize it); and an unchanging
+store can conflict with a non-unchanging read.  This means we must make
+conservative assumptions when chosing the value of this flag for a
+memory reference to an object containing both unchanging and
+non-unchanging fields: we must set the flag when writing to the object
+and clear it when reading from the object.
+
+Stored in the @code{unchanging} field and printed as @samp{/u}.
 
 @findex SCHED_GROUP_P
 @cindex @code{insn} and @samp{/s}