public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kdevel at vogtner dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60843] New: Documentation: 4.5 Integers/C99 6.3.1.3 ("reduce modulo 2^N")
Date: Tue, 15 Apr 2014 10:22:00 -0000	[thread overview]
Message-ID: <bug-60843-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60843
           Summary: Documentation: 4.5 Integers/C99 6.3.1.3 ("reduce
                    modulo 2^N")
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kdevel at vogtner dot de

Section 4.5 states [1]:

"The result of, or the signal raised by, converting an integer to a signed
integer type when the value cannot be represented in an object of that type
(C90 6.2.1.2, C99 6.3.1.3).

For conversion to a type of width N, the value is reduced modulo 2^N to be
within range of the type; no signal is raised."

Reduce A modulo M usually means find the least integer R in the range [0, M -
1] such that A is congruent R modulo M. But this is not what gcc compiled
programs do on i686/x86_64: One finds e.g. (int) 2147483649u == -2147483647.
The original bits are taken "as is", which equivalents to *subtraction* of 2^N
(N=32) giving -2147483647.

[1] http://gcc.gnu.org/onlinedocs/gcc-4.8.2/gcc/Integers-implementation.html


             reply	other threads:[~2014-04-15 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 10:22 kdevel at vogtner dot de [this message]
2014-04-29 22:40 ` [Bug other/60843] " joseph at codesourcery dot com
2014-04-30 10:30 ` kdevel at vogtner dot de
2014-04-30 21:52 ` joseph at codesourcery dot com

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=bug-60843-4@http.gcc.gnu.org/bugzilla/ \
    --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).