[Bug analyzer/110483] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL

2023-06-30 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE  ---
> --- Comment #1 from David Malcolm  ---
> Thanks for filing this; sorry about the failures.
>
> What's the endianness of the hosts that this is happening on?

Solaris/SPARC and AIX are both big endian, while avr and pru are little
endian.  As I said, without full access to the logs its hard to tell if
the failure is always the same.

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

There are gcc (Solaris 11.4/SPARC) and gcc211 (Solaris 11.3/SPARC, so
you'd need to configure with --enable-obsolete), as well as gcc111 (AIX
7.1.1) and gcc119 (AIX 7.2.2).  However, I've run my Solaris builds on
local machines.

> so presumably an issue with:
>
>  fmt_styled_string (sm, "[%li]",
> byte_idx.ulow ()));
> on those hosts.
>
> Possibly an endianness-handling mistake by me?

It certainly smells like that.

[Bug analyzer/110483] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL

2023-06-29 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483

--- Comment #1 from David Malcolm  ---
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 , const bit_to_table_map ,
style_manager ,
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 (_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?

[Bug analyzer/110483] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL

2023-06-29 Thread ro at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483

Rainer Orth  changed:

   What|Removed |Added

   Target Milestone|--- |14.0