[Bug gcov-profile/120634] Memory leak in prime-paths.cc selftests (and possibly in general?)

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120634

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jorgen Kvalsvik <j...@gcc.gnu.org>:

https://gcc.gnu.org/g:69725b13e9dc8bdb17ec8a7d554071b6b517ad47

commit r16-1591-g69725b13e9dc8bdb17ec8a7d554071b6b517ad47
Author: Jørgen Kvalsvik <j...@lambda.is>
Date:   Thu Jun 19 21:00:07 2025 +0200

    Use auto_vec in prime paths selftests [PR120634]

    The selftests had a bunch of memory leaks that showed up in make
    selftest-valgrind as a result of not using auto_vec or other
    explicitly calling release. Replacing vec with auto_vec makes the
    problem go away.  The auto_vec_vec helper is made constructable from a
    vec so that objects returned from functions can be automatically
    managed too.

            PR gcov-profile/120634

    gcc/ChangeLog:

            * prime-paths.cc (struct auto_vec_vec): Add constructor from
            vec.
            (test_split_components): Use auto_vec_vec.
            (test_scc_internal_prime_paths): Ditto.
            (test_scc_entry_exit_paths): Ditto.
            (test_complete_prime_paths): Ditto.
            (test_entry_prime_paths): Ditto.
            (test_singleton_path): Ditto.