From: Matt Wette <matt.wette@gmail.com>
To: 25791@debbugs.gnu.org
Subject: bug#25791: atomics on macOS
Date: Mon, 20 Feb 2017 14:18:27 -0800 [thread overview]
Message-ID: <C0095E00-9ACD-4A79-9D9C-76F3D64B3289@gmail.com> (raw)
In-Reply-To: <3a6373cd-2b5a-4974-963b-4e3d4dbc0048@me.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
I saw this too and gave up trying to fix it. I think this needs to be worked bottom up: I believe the C99 standard is specific about the type qualifier _Atomic being present for the first argument. The workaround for now IMO, is to change atomics-internal.h from this:
#ifdef HAVE_STDATOMIC_H
to this:
#if (defined HAVE_STDATOMIC_H) && (!defined __clang__)
By the way, gcc is forgiving here.
Matt
[-- Attachment #2: Type: text/html, Size: 2369 bytes --]
next prev parent reply other threads:[~2017-02-20 22:18 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 ` Matt Wette [this message]
2017-03-01 16:43 ` Andy Wingo
2017-03-14 12:06 ` Andy Wingo
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=C0095E00-9ACD-4A79-9D9C-76F3D64B3289@gmail.com \
--to=matt.wette@gmail.com \
--cc=25791@debbugs.gnu.org \
/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).