public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Joe Buck <jbuck@synopsys.COM>
Cc: Bernd Schmidt <bernds@redhat.com>,  <gcc@gcc.gnu.org>
Subject: Re: Complex integer division
Date: Thu, 08 Nov 2001 12:58:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0111192037240.16288-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200111191550.HAA24738@atrus.synopsys.com>

On Mon, 19 Nov 2001, Joe Buck wrote:

> The only problematic operation is division, as complex ints are closed
> (modulo overflow) for +, -, and *.  So deprecate only the problematic
> operation.

Multiplication could cause problems as well, since GCC might optimize
intermediate computations on the basis that signed integer overflow is
undefined and so fail to produce the correct answer when that is within
range.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

      reply	other threads:[~2001-11-19 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 14:23 Joseph S. Myers
2001-11-05 15:31 ` Bernd Schmidt
2001-11-07 12:21   ` Joseph S. Myers
2001-11-07 19:06   ` Joe Buck
2001-11-08 12:58     ` Joseph S. Myers [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=Pine.LNX.4.33.0111192037240.16288-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=bernds@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.COM \
    /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).