[Bug sanitizer/114956] [11/12 Regression] Segmentation fault with -fsanitize=address -fsanitize=null -O2 when attribute no_sanitize_address is enabled since r9-5742

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:25bd98dfd99e92c57ff393d393f54d028d7f86f4

commit r12-10529-g25bd98dfd99e92c57ff393d393f54d028d7f86f4
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 7 21:29:14 2024 +0200

    tree-inline: Remove .ASAN_MARK calls when inlining functions into
no_sanitize callers [PR114956]

    In r9-5742 we've started allowing to inline always_inline functions into
    functions which have disabled e.g. address sanitization even when the
    always_inline function is implicitly from command line options sanitized.

    This mostly works fine because most of the asan instrumentation is done
only
    late after ipa, but as the following testcase the .ASAN_MARK ifn calls
    gimplifier adds can result in ICEs.

    Fixed by dropping those during inlining, similarly to how we drop
    .TSAN_FUNC_EXIT calls.

    2024-05-07  Jakub Jelinek  <jakub@redhat.com>

            PR sanitizer/114956
            * tree-inline.cc: Include asan.h.
            (copy_bb): Remove also .ASAN_MARK calls if id->dst_fn has
asan/hwasan
            sanitization disabled.

            * gcc.dg/asan/pr114956.c: New test.

    (cherry picked from commit d4e25cf4f7c1f51a8824cc62bbb85a81a41b829a)