unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Thread+GC issues on ARM
Date: Fri, 06 Jan 2012 21:32:03 -0600	[thread overview]
Message-ID: <87y5tkmbm4.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <8739bsi952.fsf@pobox.com> (Andy Wingo's message of "Sat, 07 Jan 2012 02:39:05 +0100")

Andy Wingo <wingo@pobox.com> writes:

> On Sat 24 Dec 2011 13:50, Neil Jerram <neil@ossau.homelinux.net> writes:
>
>> Just in case anyone else is looking at this too, I just wanted to
>> announce that I'm investigating why the Debian Guile 2.0.3 fails to pass
>> 'make check' on ARM
>
> How's it going? :-)

If I recall correctly, there are a few of other problems too, if anyone
has time to investigate:

  https://buildd.debian.org/status/package.php?p=guile-2.0&suite=sid

ia64:
  CC     libguile_2.0_la-threads.lo
  threads.c: In function 'guilify_self_1':
  threads.c:524:39: error: 'struct GC_stack_base' has no member named 'reg'

s390:
  FAIL: threads.test: mutex-ownership: mutex with owner not retained
  (bug #27450)

s390x:
  PASS: test-asmobs
  Backtrace:
  In ice-9/boot-9.scm:
   162: 10 [catch #t #<catch-closure 802835a0> ...]
   170: 9 [#<procedure 802273c0 ()>]
  In unknown file:
     ?: 8 [catch-closure]
  In ice-9/boot-9.scm:
    62: 7 [call-with-prompt prompt0 ...]
  In ice-9/eval.scm:
   389: 6 [eval # #]
  In ice-9/boot-9.scm:
  2095: 5 [save-module-excursion #<procedure 8022a300 at ice-9/boot-9.scm:3520:3 ()>]
  3527: 4 [#<procedure 8022a300 at ice-9/boot-9.scm:3520:3 ()>]
  1368: 3 [%start-stack load-stack ...]
  1373: 2 [#<procedure 802aacc0 ()>]
  In unknown file:
     ?: 1 [primitive-load "/build/buildd-guile-2.0_2.0.3+1-2-s390x-EaW1TS/guile-2.0-2.0.3+1/test-suite/standalone/./test-ffi"]
     ?: 0 [scm-error misc-error #f ...]

  ERROR: In procedure scm-error:
  ERROR: incorrect result (7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7)

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  reply	other threads:[~2012-01-07  3:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24 12:50 Thread+GC issues on ARM Neil Jerram
2012-01-07  1:39 ` Andy Wingo
2012-01-07  3:32   ` Rob Browning [this message]
2012-01-07 12:01     ` Neil Jerram
2012-01-07 12:35       ` Neil Jerram
2012-01-07 17:52         ` Rob Browning
2012-01-08 10:28           ` Neil Jerram
2012-02-11  3:39             ` Rob Browning
2012-02-11  9:58               ` Neil Jerram
2012-02-11 13:10                 ` Neil Jerram
2012-02-11 17:39                   ` Rob Browning
2012-02-13 22:22                     ` Neil Jerram
2012-02-11 17:38                 ` Rob Browning
2013-01-16 10:28               ` Andy Wingo
2012-01-07 16:48       ` Rob Browning

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=87y5tkmbm4.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).