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 tree-optimization/108655] [13 Regression] ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649
Date: Mon, 06 Feb 2023 08:06:35 +0000	[thread overview]
Message-ID: <bug-108655-4-rrN7zpLE5o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108655-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS 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:5df573f76bb9b42231e722145033c548a5fcdf9a

commit r13-5708-g5df573f76bb9b42231e722145033c548a5fcdf9a
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Feb 6 09:05:56 2023 +0100

    ubsan: Fix up another spot that should have been BUILT_IN_UNREACHABLE_TRAPS
[PR108655]

    We ICE on the following testcase, because ivcanon calls
    gimple_build_builtin_unreachable but doesn't expect it would need vops.
    BUILT_IN_UNREACHABLE_TRAP I've introduced yesterday doesn't need
    vops and should be used in that case instead of BUILT_IN_TRAP which
    needs them.

    2023-02-06  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/108655
            * ubsan.cc (sanitize_unreachable_fn): For -funreachable-traps
            or -fsanitize=unreachable -fsanitize-trap=unreachable return
            BUILT_IN_UNREACHABLE_TRAP decl rather than BUILT_IN_TRAP.

            * gcc.dg/pr108655.c: New test.

  parent reply	other threads:[~2023-02-06  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  9:13 [Bug c++/108655] New: " marxin at gcc dot gnu.org
2023-02-03  9:14 ` [Bug c++/108655] " marxin at gcc dot gnu.org
2023-02-03 10:45 ` [Bug tree-optimization/108655] [13 Regression] " jakub at gcc dot gnu.org
2023-02-03 10:56 ` jakub at gcc dot gnu.org
2023-02-06  8:06 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-06  8:07 ` 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-108655-4-rrN7zpLE5o@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).