https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125094
Bug ID: 125094
Summary: RFE: show explanations of where zero values come based
on value_range/range_op logic
Product: gcc
Version: 17.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Target Milestone: ---
Splitting out from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124217#c1
Idea (based on the example in bug 124433): it would be really cool to explain
why the divisor is zero for such cases e.g.:
7 | do c %= (5ull << 40) & m;
| ~~~~~~~~~~~~~~~~
| |
| divisor is zero
7 | do c %= (5ull << 40) & m;
| ~~~~~~^~~~~ ^
| | |
| | has range [0, 4294967295]
| has value 5497558138880
and maybe humanize these by showing them in hex:
7 | do c %= (5ull << 40) & m;
| ~~~~~~^~~~~ ^
| | |
| | has range [0, 0xffffffff]
| has value 0x50000000000
and maybe humanize further by breaking up digit groups:
7 | do c %= (5ull << 40) & m;
| ~~~~~~^~~~~ ^
| | |
| | has range [0, 0xffff_ffff]
| has value 0x500_0000_0000