public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/114408] [13 Regression] ICE when invoking strcmp multiple times with -fsanitize=undefined -O1 -fanalyzer -flto Date: Sat, 23 Mar 2024 14:00:01 +0000 [thread overview] Message-ID: <bug-114408-4-HJcxIznr5e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114408-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114408 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[13/14 Regression] ICE when |[13 Regression] ICE when |invoking strcmp multiple |invoking strcmp multiple |times with |times with |-fsanitize=undefined -O1 |-fsanitize=undefined -O1 |-fanalyzer -flto |-fanalyzer -flto --- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Should be fixed on trunk by the above patch. The ICE was introduced by r13-5261-g0d6f7b1dd62e9c9dccb0b9b673f9cc3238b7ea6d when fixing bug 108455. Keeping open to track backporting to GCC 13.
next prev parent reply other threads:[~2024-03-23 14:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-20 15:26 [Bug ipa/114408] New: Crash " gabravier at gmail dot com 2024-03-21 9:35 ` [Bug analyzer/114408] [13/14 Regression] ICE " rguenth at gcc dot gnu.org 2024-03-22 12:35 ` law at gcc dot gnu.org 2024-03-22 15:09 ` dmalcolm at gcc dot gnu.org 2024-03-22 16:52 ` jakub at gcc dot gnu.org 2024-03-22 16:56 ` jakub at gcc dot gnu.org 2024-03-22 18:34 ` dmalcolm at gcc dot gnu.org 2024-03-23 13:53 ` cvs-commit at gcc dot gnu.org 2024-03-23 14:00 ` dmalcolm at gcc dot gnu.org [this message] 2024-05-09 17:12 ` [Bug analyzer/114408] [13 " cvs-commit at gcc dot gnu.org 2024-05-09 17:49 ` [Bug analyzer/114408] " dmalcolm 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-114408-4-HJcxIznr5e@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: linkBe 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).