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: Wed, 30 Apr 2014 21:52:00 -0000	[thread overview]
Message-ID: <bug-60843-4-e4s8gSw9iE@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 #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 30 Apr 2014, kdevel at vogtner dot de wrote:

> The problem is the erroneous wording "reduction modulo 2^N". *Reduction* by
> definition results in the least *nonnegative* number out of the list of
> congruent numbers, cf. http://www.youtube.com/watch?v=SO6l6sDwEFg&t=5m50s

It's perfectly normal English usage for "X with qualifier" to be outside 
what would be understood by X without the qualifier.  I think the use in 
the GCC manual is a perfectly ordinary and well-understood use of the 
term.  The GCC manual is not trying to refer to any particular set of 
definitions as normative references, and it's not trying to give formal 
definitions.

If anything, I'd say strictly reduction modulo 2^N is a map from Z to Z / 
2^N Z, i.e. producing an equivalence class of integers rather than a 
single integer (and for modulo arithmetic, integer types are interpreted 
as having values that are such equivalence classes).


      parent reply	other threads:[~2014-04-30 21:52 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 ` [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 [this message]

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-e4s8gSw9iE@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).