public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36402] -0x80000000 (INT_MIN) erroneously treated as unsigned
Date: Sun, 01 Jun 2008 07:26:00 -0000	[thread overview]
Message-ID: <20080601072532.18472.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36402-6266@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from ebotcazou at gcc dot gnu dot org  2008-06-01 07:25 -------
> Given that, I think a typical user would assume (as I have) that GCC would
> treat -0x80000000 as the signed value -2^31; otherwise there would seem to be
> no way to write a single constant to represent that valid value.

You're confusing the internal representation, described by the paragraph you
quoted, and the syntax of literals.  There is no bug in this case, it's the
well-know limitation of C whereby you need to write INT_MIN as (-INT_MAX - 1).


-- 

ebotcazou at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36402


  parent reply	other threads:[~2008-06-01  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31 19:39 [Bug c/36402] New: " gcczilla at achurch dot org
2008-05-31 19:50 ` [Bug c/36402] " ebotcazou at gcc dot gnu dot org
2008-06-01  4:17 ` gcczilla at achurch dot org
2008-06-01  7:26 ` ebotcazou at gcc dot gnu dot org [this message]
2008-06-01 12:22 ` joseph at codesourcery dot com
2008-06-01 14:00 ` [Bug c/36402] -0x80000000 (INT_MIN, -2147483648) " gcczilla at achurch dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080601072532.18472.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).