unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Michael Deutschmann <michael@talamasca.ocis.net>
Subject: guile-1.4.1: test failures under shared library, -O3
Date: Thu, 23 May 2002 21:42:36 -0700 (PDT)	[thread overview]
Message-ID: <%hFc78gbEN@khar-pern.talamasca.ocis.net> (raw)

I have encountered the following "make check" failure attempting
to build guile-1.4.1:

FAIL: r4rs.test: (6 9): (#<procedure leaf-eq? (x y)> (a (b (c))) ((a) b c))

I normally use maximal optimization ("-O3 -fomit-frame-pointer
-fstrict-aliasing") to compile programs, and found that the problem does
not occur when no flags are specified.  It also doesn't happen if guile
is configured not to use shared libraries.

By swap experiments, I've narrowed the problem to "continuations.c".  If
this file is compiled with "-fPIC" and "-O3", the test suite will not
succeed. If "-fomit-frame-pointer" is also specifed, the above test
failure will occur -- otherwise, the test suite will segfault.

Versions:
i486-pc-linux-gnu
linux-2.0.40rc4
glibc-2.1.3
gcc-2.95.3

---- Michael Deutschmann <michael@talamasca.ocis.net>

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2002-05-24  4:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24  4:42 Michael Deutschmann [this message]
2002-06-16 22:59 ` guile-1.4.1: test failures under shared library, -O3 Thien-Thi Nguyen
2002-06-17  2:12   ` Michael Deutschmann
2002-06-29 19:31     ` Thien-Thi Nguyen

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=%hFc78gbEN@khar-pern.talamasca.ocis.net \
    --to=michael@talamasca.ocis.net \
    /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).