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 analyzer/110882] [13 Regression] ICE with -fanalyzer on zero-sized array
Date: Thu, 09 May 2024 17:11:32 +0000 [thread overview]
Message-ID: <bug-110882-4-NNkbYWPUMm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110882-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110882
--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by David Malcolm
<dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:44968a0e00f656e9bb3e504bb2fa1a8282002015
commit r13-8748-g44968a0e00f656e9bb3e504bb2fa1a8282002015
Author: David Malcolm <dmalcolm@redhat.com>
Date: Thu May 9 13:09:28 2024 -0400
testsuite, analyzer: add test case [PR108171]
The ICE in PR analyzer/108171 appears to be a dup of the recently fixed
PR analyzer/110882 and is likewise fixed by it; adding this test case.
gcc/testsuite/ChangeLog:
PR analyzer/108171
* gcc.dg/analyzer/pr108171.c: New test.
(cherry picked from commit r14-2957-gf80efa49b7a163)
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2024-05-09 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 22:23 [Bug analyzer/110882] New: " dmalcolm at gcc dot gnu.org
2023-08-02 22:23 ` [Bug analyzer/110882] " dmalcolm at gcc dot gnu.org
2023-08-02 22:24 ` dmalcolm at gcc dot gnu.org
2023-08-03 13:48 ` [Bug analyzer/110882] [13/14 Regression] " cvs-commit at gcc dot gnu.org
2023-08-03 13:54 ` [Bug analyzer/110882] [13 " dmalcolm at gcc dot gnu.org
2023-08-03 14:47 ` cvs-commit at gcc dot gnu.org
2023-08-03 14:53 ` dmalcolm at gcc dot gnu.org
2023-10-17 10:28 ` rguenth at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-09 17:52 ` [Bug analyzer/110882] " 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-110882-4-NNkbYWPUMm@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).