From: Matt Wette <matt.wette@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: GNU Guile 2.1.5 released (beta)
Date: Fri, 16 Dec 2016 19:07:49 -0800 [thread overview]
Message-ID: <4060B5E1-5E6B-400C-ABDC-C2A9BEB3E875@gmail.com> (raw)
In-Reply-To: <87k2azuxbb.fsf@dustycloud.org>
> On Dec 16, 2016, at 6:03 PM, Christopher Allan Webber <cwebber@dustycloud.org> wrote:
>
> Matt Wette writes:
>
>>> On Dec 16, 2016, at 5:50 AM, Matt Wette <matt.wette@gmail.com> wrote:
>>>
>>> OK. This is gonna be hard to trace down.
>>>
>>> I am on a Mac running Sierra, 10.12.2. At work I am running 10.9 I believe, and I see the same behavior.
>>>
>>>
>>> If I compile with gcc 6.2 or gcc4.9, but no extra flags besides —prefix, I get the following failure:
>>>
>>> FAIL: numbers.test: string->number: valid complex number strings
>>>
>>> and trace this down to
>>>
>>> meta/guile -c '(display (eqv? (imag-part (string->number "#i1@-0")) -0.0))' => #f
>>
>> I am now compiling with clang-3.9 and getting fatal errors. Stay tuned …
>
> Is clang supported? I didn't think it was.
>
Maybe not, but it provides additional checks that may be catching something. The error that is coming up is with respect to atomics in atomics-internal.h. I believe C11 requires that the pointer arguments be _Atomic but they are not. I am trying to build w/o the atomic routines (using clang), but will retry with gcc.
next prev parent reply other threads:[~2016-12-17 3:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 19:55 GNU Guile 2.1.5 released (beta) Andy Wingo
2016-12-09 15:28 ` Matt Wette
2016-12-09 17:25 ` Christopher Allan Webber
2016-12-10 13:16 ` Matt Wette
2016-12-11 14:52 ` Matt Wette
2016-12-11 15:42 ` Matt Wette
2017-01-08 22:50 ` Andy Wingo
2016-12-11 15:17 ` Matt Wette
2016-12-12 13:45 ` Matt Wette
2016-12-12 20:46 ` Matt Wette
2016-12-13 1:24 ` dsmich
2016-12-13 21:26 ` Freja Nordsiek
2016-12-16 13:50 ` Matt Wette
2016-12-16 14:05 ` Matt Wette
2016-12-17 2:03 ` Christopher Allan Webber
2016-12-17 3:07 ` Matt Wette [this message]
2016-12-11 20:35 ` Matt Wette
2016-12-12 1:25 ` Matt Wette
2016-12-12 11:14 ` tomas
2017-01-08 22:54 ` Andy Wingo
2017-01-09 0:13 ` Matt Wette
2016-12-20 15:00 ` Matt Wette
2016-12-20 22:58 ` Matt Wette
2017-01-08 23:01 ` Andy Wingo
2017-01-08 23:28 ` Matt Wette
[not found] <mailman.109.1481389218.15985.guile-devel@gnu.org>
2016-12-10 17:11 ` Daniel Llorens
2016-12-11 0:42 ` Matt Wette
2016-12-29 19:38 ` Matt Wette
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=4060B5E1-5E6B-400C-ABDC-C2A9BEB3E875@gmail.com \
--to=matt.wette@gmail.com \
--cc=cwebber@dustycloud.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).