2004-12-18 H.J. Lu <hongjiu.lu@intel.com>

[pf3gnuchains/gcc-fork.git] / gcc / reg-notes.def

diff --git a/gcc/reg-notes.def b/gcc/reg-notes.def
index cb0343f..85a122f 100644 (file)
--- a/gcc/reg-notes.def
+++ b/gcc/reg-notes.def
@@ -21,11 +21,17 @@ Software Foundation, 59 Temple Place - Suite 330, Boston, MA
 /* This file defines all the codes that may appear on individual
    EXPR_LIST rtxes in the REG_NOTES chain of an insn.  The codes are
    stored in the mode field of the EXPR_LIST.  Source files define
-   DEF_INSN_NOTE appropriately before including this file.  */
+   DEF_REG_NOTE appropriately before including this file.  */
 
 /* Shorthand.  */
 #define REG_NOTE(NAME) DEF_REG_NOTE (REG_##NAME)
 
+/* REG_DEP_TRUE is used in LOG_LINKS to represent a read-after-write
+   dependency (i.e. a true data dependency).  This is here, not
+   grouped with REG_DEP_ANTI and REG_DEP_OUTPUT, because some passes
+   use a literal 0 for it.  */
+REG_NOTE (DEP_TRUE)
+
 /* The value in REG dies in this insn (i.e., it is not needed past
    this insn).  If REG is set in this insn, the REG_DEAD note may,
    but need not, be omitted.  */
@@ -92,9 +98,7 @@ REG_NOTE (CC_USER)
 REG_NOTE (LABEL)
 
 /* REG_DEP_ANTI and REG_DEP_OUTPUT are used in LOG_LINKS to represent
-   write-after-read and write-after-write dependencies respectively.
-   Data dependencies, which are the only type of LOG_LINK created by
-   flow, are represented by a 0 reg note kind.  */
+   write-after-read and write-after-write dependencies respectively.  */
 REG_NOTE (DEP_ANTI)
 REG_NOTE (DEP_OUTPUT)