public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/98073] error: in can_merge_p, at analyzer/region-model.cc Date: Tue, 01 Dec 2020 10:23:34 +0000 [thread overview] Message-ID: <bug-98073-4-XKdWJuUp02@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98073-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98073 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Reduced test-case: struct ist { char ptr; long len } __trans_tmp_1, http_update_host_authority; http_update_host_sl_0_0_0; http_update_host(const struct ist uri) { uri.len || uri.ptr; if (http_update_host_sl_0_0_0) { http_update_host_authority = __trans_tmp_1; !http_update_host_authority.len; } else http_update_host_authority = uri; }
next prev parent reply other threads:[~2020-12-01 10:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-01 2:54 [Bug analyzer/98073] New: " rnsanchez at gmail dot com 2020-12-01 10:19 ` [Bug analyzer/98073] " marxin at gcc dot gnu.org 2020-12-01 10:23 ` marxin at gcc dot gnu.org [this message] 2021-01-06 1:54 ` cvs-commit at gcc dot gnu.org 2021-01-06 2:03 ` 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-98073-4-XKdWJuUp02@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).