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/96798] Analyzer failures on Darwin Date: Mon, 31 Aug 2020 22:31:39 +0000 [thread overview] Message-ID: <bug-96798-4-8AViK9a8RE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96798-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798 --- Comment #10 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:ee7bfbe5eb70a23bbf3a2cedfdcbd2ea1a20c3f2 commit r11-2956-gee7bfbe5eb70a23bbf3a2cedfdcbd2ea1a20c3f2 Author: David Malcolm <dmalcolm@redhat.com> Date: Mon Aug 31 16:20:55 2020 -0400 analyzer: gather builtin/internal fn handling into switch statements Clean up this code in preparation for fixing PR analyzer/96798. gcc/analyzer/ChangeLog: * region-model.cc (region_model::on_call_pre): Gather handling of builtins and of internal fns into switch statements. Handle "alloca" and BUILT_IN_ALLOCA_WITH_ALIGN.
next prev parent reply other threads:[~2020-08-31 22:31 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-26 12:48 [Bug analyzer/96798] New: " dominiq at lps dot ens.fr 2020-08-27 22:49 ` [Bug analyzer/96798] " dmalcolm at gcc dot gnu.org 2020-08-27 23:30 ` dominiq at lps dot ens.fr 2020-08-28 10:10 ` dmalcolm at gcc dot gnu.org 2020-08-28 11:20 ` dominiq at lps dot ens.fr 2020-08-28 22:39 ` dominiq at lps dot ens.fr 2020-08-29 0:58 ` dmalcolm at gcc dot gnu.org 2020-08-29 7:02 ` iains at gcc dot gnu.org 2020-08-29 7:21 ` iains at gcc dot gnu.org 2020-08-29 7:22 ` iains at gcc dot gnu.org 2020-08-31 22:31 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-31 22:32 ` cvs-commit at gcc dot gnu.org 2020-08-31 22:47 ` dmalcolm at gcc dot gnu.org 2020-09-11 1:09 ` cvs-commit at gcc dot gnu.org 2020-09-11 1:13 ` 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-96798-4-8AViK9a8RE@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).