This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Immediate uses checked in
Some typos.
>
> ! Operands use to be updated lazily via calls to @code{get_stmt_operands}.
^^^
s/use/used/
> ! This function is now deprecated and operands are updated as soon as the stmt is
s/stmt/statement/
> ! finished via a call to @code{update_stmt}. If statement elements are
> ! changed via @code{SET_USE} or @code{SET_DEF}, no further action need be
> ! taken (ie, those macros take care of whatever updating is required). If
s/need be/need to be/
> + @item @code{num_imm_uses (ssa_var)} : Returns the number of immediate uses of
> + @code{ssa_var}. Its better not to use this if possible since it simply
s/Its/It's/
> +
> + It is also still possible to utilize lazy updating of stmts, but this should be used only when absolutely required. Both alias analysis and the dominator
This line is too long. I think that even for the .texi files we have
the 80 column limit.
s/stmts/statements/
> + optimizations currently do this.
> +
> + When lazy updating is being used, the immediate use information is out of date
> + and cannot be used reliably. Lazy updating is acheived by simply marking stmts
s/acheived/achieved/
s/stmts/statements/
> + modified via calls to @code{mark_stmt_modified} instead of @code{update_stmt}.
> + When lazy updating is no longer required, all the modified stmts must have
s/stmts/statements/