From: Gary Houston <ghouston@arglist.com>
Subject: gcc optimisation breaks guile floating point
Date: 27 Aug 2002 22:10:25 +0100 [thread overview]
Message-ID: <200208272110.OAA20247@onyx.he.net> (raw)
Floating point seems somewhat broken in latest CVS if compiled with
recent gcc (e.g., version 3.2):
guile> 3.2
0.0
The problem is in libguile/numbers.c:scm_make_real, and only if
scm_double_cell is inlined (so it isn't a problem in Guile 1.5).
Compiling with the -fno-strict-aliasing option fixes it. Here's a
similar kind of problem code:
#include <stdlib.h>
#include <string.h>
static void * make_z (double x)
{
void *z = malloc (50);
memset (z, 0, 50);
*((unsigned long *) z) = 0;
*((double *) z) = x;
return z;
}
main ()
{
void *z = make_z (3.2);
double d = *((double *) z);
int i;
for (i = 0; i < sizeof (double); i++)
{
printf ("%d\n", ((unsigned char *) &d)[i]);
}
return 0;
}
Apparently, "according to ANSI C" (no direct quotation available), the
compiler can assume that *((unsigned long *) z) and *((double *) z)
refer to different locations and reorder the statements!
I don't know what would be needed to make Guile conform to such
stringent interpretation of the standard, but I don't think it would
be easy to determine that it was correct and that it would always stay
that way. Perhaps we should just add the -fno-strict-aliasing option
if the compiler supports it?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-08-27 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 21:10 Gary Houston [this message]
2002-08-27 22:30 ` gcc optimisation breaks guile floating point Han-Wen Nienhuys
2002-08-28 20:26 ` Marius Vollmer
2002-08-28 22:53 ` Han-Wen Nienhuys
2002-08-30 17:44 ` Gary Houston
2002-09-05 21:10 ` Han-Wen Nienhuys
2002-09-12 1:46 ` Carl R. Witty
2002-09-13 21:20 ` Han-Wen Nienhuys
2002-09-24 22:32 ` Gary Houston
[not found] ` <200209242233.PAA04201@onyx.he.net>
2002-10-02 22:40 ` Marius Vollmer
2002-10-02 23:34 ` Gary Houston
[not found] ` <200210022336.QAA18265@onyx.he.net>
2002-10-03 12:33 ` 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=200208272110.OAA20247@onyx.he.net \
--to=ghouston@arglist.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).