From: davidm@mostang.com (David Mosberger-Tang)
Subject: bug in throw.c
Date: Sun, 6 Apr 2003 17:01:36 -0700 (PDT) [thread overview]
Message-ID: <20030407000136.0F81D8B7@panda.mostang.com> (raw)
Hi,
Today I tried to build guile-1.6.3 on ia64 linux but it failed during
the build when trying to use guile to generate some documentation.
Subsequently, I tried the snapshot from April 4th and it had the same
problem. The problem is quite obvious: in throw.c, we find:
#if 0/*def __GNUC__*/
/* Dirk:FIXME:: This bugfix should be removed some time. */
/* GCC 2.95.2 has a bug in its optimizer that makes it generate
incorrect code sometimes. This barrier stops it from being too
clever. */
asm volatile ("" : "=g" (winds));
#endif
This is clearly bogus: the asm statement claims that it's writing the
"winds" variable, which isn't true. On ia64, this has the effect that
the "winds" gets corrupted and comes out with value "1". Just
disabling the workaround fixes the issue. Perhaps the workaround is
legitimate for some platforms, but I suspect it should always be
disabled for gcc v3.x or newer.
--david
--- libguile/throw.c~ Thu Mar 14 16:00:40 2002
+++ libguile/throw.c Sun Apr 6 16:56:58 2003
@@ -622,7 +622,7 @@
}
}
-#ifdef __GNUC__
+#if 0/*def __GNUC__*/
/* Dirk:FIXME:: This bugfix should be removed some time. */
/* GCC 2.95.2 has a bug in its optimizer that makes it generate
incorrect code sometimes. This barrier stops it from being too
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-04-07 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 0:01 David Mosberger-Tang [this message]
2003-04-08 6:31 ` bug in throw.c Christopher Cramer
2003-04-08 6:44 ` David Mosberger-Tang
2003-04-11 3:24 ` Rob Browning
2003-05-03 21:47 ` Marius Vollmer
2003-05-03 21:56 ` 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=20030407000136.0F81D8B7@panda.mostang.com \
--to=davidm@mostang.com \
--cc=David.Mosberger@acm.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).