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/110455] [14 Regression] tree check: expected none of vector_type, have vector_type in get_gassign_result, at analyzer/region-model.cc:870 with -fanalyzer Date: Fri, 21 Jul 2023 00:29:06 +0000 [thread overview] Message-ID: <bug-110455-4-9JIsVs64Xl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110455-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110455 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:a4913a19d24a794c97f38d9c65c47c1fb9f2140c commit r14-2690-ga4913a19d24a794c97f38d9c65c47c1fb9f2140c Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Jul 20 20:24:10 2023 -0400 analyzer: avoid usage of TYPE_PRECISION on vector types [PR110455] gcc/analyzer/ChangeLog: PR analyzer/110455 * region-model.cc (region_model::get_gassign_result): Only check for bad shift counts when dealing with an integral type. gcc/testsuite/ChangeLog: PR analyzer/110455 * gcc.dg/analyzer/pr110455.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-07-21 0:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 11:27 [Bug analyzer/110455] New: tree check: expected none of vector_type, have vector_type in get_gassign_result, at analyzer/region-model.cc:870 with -fanalyzer[14 Regression] ICE: zsojka at seznam dot cz 2023-06-28 18:29 ` [Bug analyzer/110455] [14 Regression] " pinskia at gcc dot gnu.org 2023-07-21 0:29 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-21 0:37 ` [Bug analyzer/110455] [14 Regression] tree check: expected none of vector_type, have vector_type in get_gassign_result, at analyzer/region-model.cc:870 with -fanalyzer 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-110455-4-9JIsVs64Xl@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).