https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
Tim Lange changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
--- Comment #5 from CVS Commits ---
The master branch has been updated by Tim Lange :
https://gcc.gnu.org/g:0ea5e3f4542832b8da016b152695e64a2a386309
commit r13-2582-g0ea5e3f4542832b8da016b152695e64a2a386309
Author: Tim Lange
Date: Sat Sep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
Tim Lange changed:
What|Removed |Added
Assignee|dmalcolm at gcc dot gnu.org|tlange at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
--- Comment #4 from David Malcolm ---
(In reply to Tim Lange from comment #3)
> It seems to me that the implementations of byte_range/bit_range
> get_last_byte_offset () already assume that m_size_in_bytes should be
> greater than zero. So I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
--- Comment #3 from Tim Lange ---
Thanks for the report!
(In reply to David Malcolm from comment #2)
> (gdb) call this->dump()
> bytes 1-0
This should be the read_bytes in region_model::check_region_bounds, with the
start being the offset and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
--- Comment #2 from David Malcolm ---
Failing assertion here:
#1 0x014df116 in ana::byte_range::exceeds_p (this=0x7fffbf80,
other=..., out_overhanging_byte_range=0x7fffbfc0)
at ../../src/gcc/analyzer/store.cc:464
464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-09-06
CC|
