[Bug analyzer/106413] State explosion on va_arg when va_start is in top-level function of analysis

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

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalc...@gcc.gnu.org>:

https://gcc.gnu.org/g:6d5194a10dc103031b9c8a03091ca70f6db33c8b

commit r13-1807-g6d5194a10dc103031b9c8a03091ca70f6db33c8b
Author: David Malcolm <dmalc...@redhat.com>
Date:   Fri Jul 22 19:50:54 2022 -0400

    analyzer: fix state explosion on va_arg [PR106413]

    Fix state explosion on va_arg when the call to va_start is in the
    top-level function of the analysis.

    gcc/analyzer/ChangeLog:
            PR analyzer/106413
            * varargs.cc (region_model::impl_call_va_start): Avoid iterating
            through non-existant variadic arguments by initializing the
            impl_region to "UNKNOWN" if the va_start occurs in the top-level
            function to the analysis.

    gcc/testsuite/ChangeLog:
            PR analyzer/106413
            * gcc.dg/analyzer/torture/stdarg-4.c: New test.

    Signed-off-by: David Malcolm <dmalc...@redhat.com>