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/110483] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL
Date: Thu, 29 Jun 2023 20:22:59 +0000	[thread overview]
Message-ID: <bug-110483-4-R7wyWnjBSk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110483-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this; sorry about the failures.

What's the endianness of the hosts that this is happening on?

Is there a machine in the GCC compile farm that this happens on?

The row of indices is is created here in
string_region_spatial_item::make_table:
    if (m_show_full_string)
      {
       for (byte_offset_t byte_idx = bytes.get_start_byte_offset ();
            byte_idx < bytes.get_next_byte_offset ();
            byte_idx = byte_idx + 1)
         add_column_for_byte (t, btm, sm, byte_idx,
                              byte_idx_table_y, byte_val_table_y);
where class string_region_spatial_item has:
  void add_column_for_byte (table &t, const bit_to_table_map &btm,
                            style_manager &sm,
                            const byte_offset_t byte_idx,
                            const int byte_idx_table_y,
                            const int byte_val_table_y) const
  {
    tree string_cst = get_string_cst ();
    gcc_assert (byte_idx >= 0);
    gcc_assert (byte_idx < TREE_STRING_LENGTH (string_cst));

    const byte_range bytes (byte_idx, 1);
    if (1) // show_byte_indices
      {
        const table::rect_t idx_table_rect
          = btm.get_table_rect (&m_string_reg, bytes, byte_idx_table_y, 1);
        t.set_cell_span (idx_table_rect,
                         fmt_styled_string (sm, "[%li]",
                                            byte_idx.ulow ()));
      }

so presumably an issue with:

                         fmt_styled_string (sm, "[%li]",
                                            byte_idx.ulow ()));
on those hosts.

Possibly an endianness-handling mistake by me?

  parent reply	other threads:[~2023-06-29 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 11:09 [Bug analyzer/110483] New: " ro at gcc dot gnu.org
2023-06-29 11:10 ` [Bug analyzer/110483] " ro at gcc dot gnu.org
2023-06-29 20:22 ` dmalcolm at gcc dot gnu.org [this message]
2023-06-30 12:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-27 22:19 ` [Bug analyzer/110483] [14 Regression] " cvs-commit at gcc dot gnu.org
2024-02-27 22:29 ` dmalcolm at gcc dot gnu.org
2024-02-29 10:30 ` ro at gcc dot gnu.org
2024-02-29 16:08 ` dmalcolm at gcc dot gnu.org
2024-02-29 20:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07  7:40 ` [Bug analyzer/110483] [14/15 " rguenth 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-110483-4-R7wyWnjBSk@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).