This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/52661] negative maxint for long long gives warning
- From: "jmichae3 at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 22 Mar 2012 20:42:39 +0000
- Subject: [Bug c/52661] negative maxint for long long gives warning
- Auto-submitted: auto-generated
- References: <bug-52661-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52661
Jim Michaels <jmichae3 at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #26949|0 |1
is obsolete| |
Attachment #26950|0 |1
is obsolete| |
--- Comment #12 from Jim Michaels <jmichae3 at yahoo dot com> 2012-03-22 20:42:39 UTC ---
Created attachment 26959
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26959
maxint-bug.cpp, additional ints showing that 64-bit only causes problem
you are looking at the model of the compiler. I am looking at the behavior
patterns of the compiler. I am learning more and more as I put in more test
cases, like now.
it seems that whether an LL or not is added to a 64-bit number ONLY it causes a
warning.
your explanation of them being separate tokens I think has no bearing on what
turns this into a long long data type. I think that once it is in this data
type, it is being mishandled.