This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/11290] New: "so large that it is unsigned" gripe #2.
- From: "i18rabbit at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Jun 2003 10:33:25 -0000
- Subject: [Bug ada/11290] New: "so large that it is unsigned" gripe #2.
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11290
Summary: "so large that it is unsigned" gripe #2.
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: i18rabbit at hotmail dot com
CC: gcc-bugs at gcc dot gnu dot org
FBSD 4.8, gcc 2.95.4 (similar to bug #7826)
when gcc encounters an integer greater than the maximum signed
integer value, it issues a warning "... so large that it is unsigned".
for example: (unsigned int)x = 4000000000; // generates warning.
as does: (unsigned int)x = (unsigned int)4000000000
but not: (unsigned int)x = 400000000U
there should be a way to specifically turn off this warning. Possibly
it's "compiler correct", but it's a mostly useless warning that clutters a "clean compile".