public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/114743] ICE in build_check_stmt at asan.cc:2707 while compiling gcc.dg/ubsan/pr112709-2.c with -fsanitize=address
Date: Wed, 17 Apr 2024 08:24:51 +0000	[thread overview]
Message-ID: <bug-114743-4-SK9sbpScex@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114743-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:299d14a54672a4d12c1abbe4031a732bb56cddaa

commit r14-10000-g299d14a54672a4d12c1abbe4031a732bb56cddaa
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Apr 17 10:24:18 2024 +0200

    asan: Don't instrument .ABNORMAL_DISPATCHER [PR114743]

    .ABNORMAL_DISPATCHER is currently the only internal function with
    ECF_NORETURN, and asan likes to instrument ECF_NORETURN calls by adding
    some builtin call before them, which breaks the .ABNORMAL_DISPATCHER
    discovery added in gsi_safe_*.

    The following patch fixes asan not to instrument .ABNORMAL_DISPATCHER
    calls, like it doesn't instrument a couple of specific builtin calls
    as well.

    2024-04-17  Jakub Jelinek  <jakub@redhat.com>

            PR sanitizer/114743
            * asan.cc (maybe_instrument_call): Don't instrument calls to
            .ABNORMAL_DISPATCHER.

            * gcc.dg/asan/pr112709-2.c (freddy): New function from
            gcc.dg/ubsan/pr112709-2.c version of the test.

  parent reply	other threads:[~2024-04-17  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 13:28 [Bug sanitizer/114743] New: " pheeck at gcc dot gnu.org
2024-04-16 13:29 ` [Bug sanitizer/114743] " pheeck at gcc dot gnu.org
2024-04-16 15:42 ` jakub at gcc dot gnu.org
2024-04-17  8:24 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-17  8:28 ` jakub at gcc dot gnu.org
2024-04-21  4:09 ` cvs-commit at gcc dot gnu.org
2024-04-23  6:43 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114743-4-SK9sbpScex@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).