unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer")
Cc: guile-devel@gnu.org
Subject: Re: 2.0.11 on OS X 10.9 / Xcode 5.1
Date: Thu, 10 Apr 2014 10:10:34 -0400	[thread overview]
Message-ID: <rmizjjte0md.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87bnwak01s.fsf@taylan.uni.cx> ("Taylan Ulrich \"Bayırlı/Kammer\""'s message of "Wed, 09 Apr 2014 17:14:07 +0200")

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]


taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:

> taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
>
>> On OS X 10.9 with Xcode 5.1, make fails unless -O0 is used; the output
>> of ./configure && make during the failure is here:
>>
>> http://sprunge.us/PLGI
>>
>> After a successful build with -O0, there are two failures during make
>> check:
>>
>> FAIL: srfi-18.test: thread-terminate!: termination destroys non-started
>> thread
>>
>> FAIL: srfi-18.test: thread-terminate!: termination destroys started
>> thread
>
> By the way, after installing GCC 4.8 from MacPorts and setting the CC
> environment variable to use it (executable "gcc-mp-4.8"), the above
> issues are resolved, but I get the following test failure now:

So it seems that either there's a bug in clang, or a bug in guile that
causes problems when compiled with clang (which has different aggressive
optimizations than gcc).  Based on anecdotes from many other packages,
it seems more likely than not that it's a guile bug.

It would be interesting to bisect compilation of guile with 2 compilers,
or to compile with clang with optimization turned way down.

[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

  parent reply	other threads:[~2014-04-10 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 19:35 2.0.11 on OS X 10.9 / Xcode 5.1 Taylan Ulrich Bayırlı/Kammer
2014-04-09 15:14 ` Taylan Ulrich Bayırlı/Kammer
2014-04-09 15:38   ` Taylan Ulrich Bayırlı/Kammer
2014-04-10 14:10   ` Greg Troxel [this message]
2014-04-11  1:08   ` Mark H Weaver
2014-04-22 14:36     ` Taylan Ulrich Bayirli/Kammer
2014-04-22 16:28       ` Mark H Weaver
2014-04-23 17:51         ` Taylan Ulrich Bayirli/Kammer
2014-04-24 14:20           ` Taylan Ulrich Bayirli/Kammer
2014-04-24 16:04           ` Mark H Weaver

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=rmizjjte0md.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=guile-devel@gnu.org \
    --cc=taylanbayirli@gmail.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).