unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ilove zfs <ilovezfs@icloud.com>
Cc: 25791-done@debbugs.gnu.org
Subject: bug#25791: address argument to atomic operation must be a pointer to _Atomic type with 2.1.7 on macOS
Date: Tue, 14 Mar 2017 13:06:39 +0100	[thread overview]
Message-ID: <8760jc83lc.fsf@pobox.com> (raw)
In-Reply-To: <87efyhdk20.fsf@pobox.com> (Andy Wingo's message of "Wed, 01 Mar 2017 17:43:35 +0100")

On Wed 01 Mar 2017 17:43, Andy Wingo <wingo@pobox.com> writes:

> On Sun 19 Feb 2017 09:41, ilove zfs <ilovezfs@icloud.com> writes:
>
>> On macOS 10.11 and 10.12 building with Xcode 8, guile 2.1.7 fails to
>> compile with several errors saying "address argument to atomic
>> operation must be a pointer to _Atomic type." I
>> can avoid this by setting ac_cv_header_stdatomic_h=no.
>>
>> Build logs here:
>> https://gist.github.com/ilovezfs/b18b7e6160e0a4c5da297cc430961f63
>> https://gist.github.com/57e1513e03ede26dc97c0f63eaad3a98
>>
>> Build failure is
>> ```
>>   CC       libguile_2.2_la-arrays.lo
>>   CC       libguile_2.2_la-async.lo
>> In file included from async.c:27:
>> ../libguile/atomics-internal.h:37:10: error: address argument to
>> atomic operation must be a pointer to _Atomic type ('gl_uint32_t *'
>> (aka 'unsigned int *') invalid)
>>   return atomic_fetch_sub (loc, arg);
>>          ^                 ~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/include/stdatomic.h:149:43:
>> note: expanded from macro 'atomic_fetch_sub'
>> #define atomic_fetch_sub(object, operand) __c11_atomic_fetch_sub(object, operand, __ATOMIC_SEQ_CST)
>> ```
>> and several similar errors.
>>
>> Previously (as of guile 2.1.4) I had been able to work around the issue without setting ac_cv_header_stdatomic_h=no with this patch:
>> https://raw.githubusercontent.com/ilovezfs/formula-patches/d2798a468346a7a28fbcd1c8aa3c1ccd5627b03f/guile/guile-atomic-type.patch
>>
>> However, the patch is no longer sufficient since now void** is one the types needing _Atomic, which isn't allowed.
>
> Any ideas here?  Sure would be nice to release a Guile with atomics that
> compiles with clang.

Fixed in 2.1.8 I think.

Andy





      reply	other threads:[~2017-03-14 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  8:41 bug#25791: address argument to atomic operation must be a pointer to _Atomic type with 2.1.7 on macOS ilove zfs
2017-02-20 22:18 ` bug#25791: atomics " Matt Wette
2017-03-01 16:43 ` bug#25791: address argument to atomic operation must be a pointer to _Atomic type with 2.1.7 " Andy Wingo
2017-03-14 12:06   ` Andy Wingo [this message]

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=8760jc83lc.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=25791-done@debbugs.gnu.org \
    --cc=ilovezfs@icloud.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).