public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60843] Documentation: 4.5 Integers/C99 6.3.1.3 ("reduce modulo 2^N")
Date: Tue, 29 Apr 2014 22:40:00 -0000 [thread overview]
Message-ID: <bug-60843-4-y7arMdlHkv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60843-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60843
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 15 Apr 2014, kdevel at vogtner dot de wrote:
> 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
I don't see the problem. It explicitly says "reduced modulo 2^N to be
within range of the type", and that unambiguously defines the result
value, as there is exactly one result within the range of the type that is
equal to the input, modulo 2^N. The qualifier "to be within range of the
type" says that [0, M - 1] is irrelevant, because that isn't the range of
the type in question.
This is the normal form of modulo arithmetic for signed types, as used for
example by -fwrapv (and defined in detail in the first (1994) edition of
LIA-1; the second (2012) edition removes the modulo operations, but the
underlying wrap_I operation is in LIA-2).
next prev parent reply other threads:[~2014-04-29 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 10:22 [Bug other/60843] New: " kdevel at vogtner dot de
2014-04-29 22:40 ` joseph at codesourcery dot com [this message]
2014-04-30 10:30 ` [Bug other/60843] " 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-y7arMdlHkv@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).