This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug other/80437] large decimal numbers in diagnostics are hard to read


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

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |trippels at gcc dot gnu.org

--- Comment #6 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #4)
> If the warning is based of a const, maybe lead with that e.g. in the 2nd
> place here:
> 
> bug.c:11:5: warning: 'memset': specified size 18446744073709551611 (aka
> 0xffff_ffff_ffff_fffb, 1<<64 - 5, SOME_CONST) exceeds maximum object size
> PTRDIFF_MAX (aka 9223372036854775807, 0x7fff_ffff_ffff_ffff, 1<<63 - 1)

Please keep it simple and don't over-engineer.
Printing all four variants looks like overkill to me.

I would simply use decimals up to a certain cut-off and hex numbers
(without underscores) above it.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]