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/96798] Analyzer failures on Darwin Date: Fri, 28 Aug 2020 10:10:54 +0000 [thread overview] Message-ID: <bug-96798-4-DnhLif51zh@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 #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Thanks. Unfortunately that didn't trigger the issue for me, sorry. I'm wondering how best to debug this. Could you attach the preprocessed source from the testcase(s) please? Also, if you hack in a call to: __analyzer_dump (); immediately *after* the call to memset in memset-1.c's test_5, what do you get? I'm seeing: rmodel: stack depth: 1 frame (index 0): frame: 'test_5'@1 clusters within frame: 'test_5'@1 cluster for: buf key: {kind: default, start: 0, size: 2048, next: 2048} value: 'char[256]' {UNKNOWN(char[256])} m_called_unknown_fn: FALSE constraint_manager: equiv classes: ec0: {(void *)0B == [m_constant]'0B'} constraints: (signifying among other things that "buf" now has unknown content, that the memset could have overwritten the earlier write to buf[42], given that "n" isn't known). Alternatively, is there a public test box available somewhere? I didn't see one in the GCC compile farm.
next prev parent reply other threads:[~2020-08-28 10:10 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 [this message] 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 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-DnhLif51zh@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).