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?
