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/111802] New analyser diagram failures since commit b365e9d57ad4
Date: Thu, 15 Feb 2024 14:58:52 +0000	[thread overview]
Message-ID: <bug-111802-4-Sjcs2oYaSB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111802-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111802

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug report.

The issue seems to be with the top line here:
                             ┌────┬────┬────┬────┬────┐┌─────┬─────┬─────┐
                             │[1] │[1] │[1] │[1] │[1] ││ [1] │ [1] │ [1] │
                             ├────┼────┼────┼────┼────┤├─────┼─────┼─────┤
                             │' ' │'w' │'o' │'r' │'l' ││ 'd' │ '!' │ NUL │
                             ├────┴────┴────┴────┴────┴┴─────┴─────┴─────┤
                             │     string literal (type: 'char[8]')      │
                             └───────────────────────────────────────────┘
where the repeated "[1]"s are meant to be 0 through 7.

Does this still affect you?

  reply	other threads:[~2024-02-15 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 19:22 [Bug analyzer/111802] New: " thiago.bauermann at linaro dot org
2024-02-15 14:58 ` dmalcolm at gcc dot gnu.org [this message]
2024-02-15 18:15 ` [Bug analyzer/111802] " thiago.bauermann at linaro dot org
2024-02-27 22:19 ` [Bug analyzer/111802] [14 Regression] " cvs-commit at gcc dot gnu.org
2024-02-27 22:29 ` dmalcolm at gcc dot gnu.org
2024-03-01 17:30 ` thiago.bauermann at linaro dot 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-111802-4-Sjcs2oYaSB@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).