This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Immediate uses checked in
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: amacleod at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org, dnovillo at redhat dot com
- Date: Fri, 08 Apr 2005 13:46:17 -0400 (EDT)
- Subject: Re: Immediate uses checked in
- References: <1112728031.3733.3.camel@pain>
Hi Andrew,
> I have just checked in the integrated immediate uses patch.
Would you care to document the new update_stmt? A quick grep for
modify_stmt shows:
doc/tree-ssa.texi:@findex modify_stmt
doc/tree-ssa.texi:modified by a call to @code{modify_stmt}. So, if your pass replaces
doc/tree-ssa.texi:operands in a statement, make sure to call @code{modify_stmt}.
tree-cfg.c:/* A list of all the noreturn calls passed to modify_stmt.
If you could also document what BREAK_FROM_SAFE_IMM_USE is for either
somewhere in the source code or in some texi, that would be great. I
am a bit worried that somebody might just use "break;" instead of
BREAK_FROM_SAFE_IMM_USE.
Or maybe we could put a link to your post?
http://gcc.gnu.org/ml/gcc-patches/2005-04/msg00164.html
which I find very useful. (But then "refer to this message for how to
use ..." sounds a bit ugly.)
Kazu Hirata