unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org, jwe@bevo.che.wisc.edu
Subject: Re: avoid potential overflow in complex division
Date: Sat, 30 Mar 2002 15:34:29 -0800	[thread overview]
Message-ID: <E16rSMf-0003CY-00@giblet> (raw)
In-Reply-To: <15493.42015.964573.785661@segfault.bogus.domain> (jwe@bevo.che.wisc.edu)

   From: "John W. Eaton" <jwe@bevo.che.wisc.edu>
   Date: Tue, 5 Mar 2002 23:07:43 -0600

   [complex div overflows when not using -O2 + patch]

thanks.  i've recorded this as bug:

  1003-complex-division-sometimes-overflows

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


       reply	other threads:[~2002-03-30 23:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15493.42015.964573.785661@segfault.bogus.domain>
2002-03-30 23:34 ` Thien-Thi Nguyen [this message]
2002-04-01  0:24   ` avoid potential overflow in complex division Marius Vollmer

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=E16rSMf-0003CY-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-devel@gnu.org \
    --cc=jwe@bevo.che.wisc.edu \
    --cc=ttn@glug.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).