Richard Biener <richard.guent...@gmail.com> writes:
> On Thu, Nov 2, 2023 at 11:25 AM Sam James <s...@gentoo.org> wrote:
>>
>>
>> Richard Biener <richard.guent...@gmail.com> writes:
>>
>> > On Thu, Nov 2, 2023 at 10:03 AM Sam James <s...@gentoo.org> wrote:
>> >>
>> >> Say 'memory lifetime' rather than 'memory life' as lifetime is the more
>> >> standard term nowadays (indeed we have e.g. -fno-lifetime-dse).
>> >>
>> >> It's also easier to grep for if someone is looking for the documentation
>> >> on
>> >> where we do that.
>> >
>> > OK
>>
>> Could you push for me please? I have a sw account but no gcc access
>> (yet).
>
> Done after fixing ChangeLog format.
>
> Richard.
Thanks!
>
>> cheers
>>
>> >
>> >> gcc/ChangeLog:
>> >> * doc/passes.texi (Dead code elimination): Explicitly say 'lifetime'
>> >> as this has become the standard term for what we're doing here.
>> >>
>> >> Signed-off-by: Sam James <s...@gentoo.org>
>> >> ---
>> >> gcc/doc/passes.texi | 2 +-
>> >> 1 file changed, 1 insertion(+), 1 deletion(-)
>> >>
>> >> diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
>> >> index eb2bb6062834..470ac498a132 100644
>> >> --- a/gcc/doc/passes.texi
>> >> +++ b/gcc/doc/passes.texi
>> >> @@ -543,7 +543,7 @@ and is defined by
>> >> @code{pass_early_warn_uninitialized} and
>> >> @item Dead code elimination
>> >>
>> >> This pass scans the function for statements without side effects whose
>> >> -result is unused. It does not do memory life analysis, so any value
>> >> +result is unused. It does not do memory lifetime analysis, so any value
>> >> that is stored in memory is considered used. The pass is run multiple
>> >> times throughout the optimization process. It is located in
>> >> @file{tree-ssa-dce.cc} and is described by @code{pass_dce}.
>> >> --
>> >> 2.42.0
>> >>
>>
