unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "John W. Eaton" <jwe@bevo.che.wisc.edu>
Cc: guile-devel@gnu.org
Subject: DINFINITY alpha not gnu/linux
Date: Mon, 16 Feb 2004 16:51:42 -0600	[thread overview]
Message-ID: <16433.18814.653327.782668@devzero.bogus.domain> (raw)
In-Reply-To: <877jymwt2b.fsf@zip.com.au>

On 17-Feb-2004, Kevin Ryde <user42@zip.com.au> wrote:

| I see numbers.c guile_ieee_init is setup to use DINFINITY on
| 
| 	defined (__alpha__) && ! defined (linux)
| 
| DINFINITY is not available on alpha freebsd.  I take it it's an
| OSF-ism.  There really wants to be an autoconf probe for DINFINITY,
| rather than cpp defines.

I think this code is probably my fault.  I took it from Octave, which
is what I originally wrote it for.

Octave now uses

  #if defined (SCO)
	volatile double tmp = 1.0;
	tmp_inf = 1.0 / (tmp - tmp);
  #elif defined (__alpha__) && defined (__osf__)
	extern unsigned int DINFINITY[2];
	tmp_inf =  (*(X_CAST(double *, DINFINITY)));
  #else
	double tmp = 1e+10;
	tmp_inf = tmp;
	for (;;)
	  {
	    tmp_inf *= 1e+10;
	    if (tmp_inf == tmp)
	      break;
	    tmp = tmp_inf;
	  }
  #endif

to define Inf, but there may be better ways to do this.  If so, please
pass the code back to Octave as well as fixing guile.

Thanks,

jwe

-- 
www.octave.org | www.che.wisc.edu/~jwe | Peace would shock and awe me.


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


  reply	other threads:[~2004-02-16 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 22:36 DINFINITY alpha not gnu/linux Kevin Ryde
2004-02-16 22:51 ` John W. Eaton [this message]
2004-02-16 23:06   ` Kevin Ryde
2004-02-16 23:41     ` John W. Eaton
2004-02-21 22:08       ` Kevin Ryde

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=16433.18814.653327.782668@devzero.bogus.domain \
    --to=jwe@bevo.che.wisc.edu \
    --cc=guile-devel@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).