From: Eric Wong <e@80x24.org>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Ben Peart <peartben@gmail.com>,
git@vger.kernel.org,
Jeff Hostetler <Jeff.Hostetler@microsoft.com>,
Ben Peart <benpeart@microsoft.com>
Subject: Re: Safe to use stdatomic.h?
Date: Tue, 21 Mar 2017 01:59:48 +0000 [thread overview]
Message-ID: <20170321015948.GC6536@starla> (raw)
In-Reply-To: <20170320232240.k3egololfj7wt5cf@genre.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> wrote:
> I could support the argument for ditching RHEL/CentOS 5 support, but I
> expect other people might disagree. After all, we're still targeting
> C89.
Yeah, I still use and support CentOS 5 in some places (but maybe
not git, still using ancient versions there, too).
Anyways, I'm still relying on the traditional __sync_* builtins
from in earlier gcc 4.x releases in some code GPL-3.0 code I
maintain for older systems:
https://gcc.gnu.org/onlinedocs/gcc/_005f_005fsync-Builtins.html
Since git is GPL-2.0, it is license-compatible with all the
atomic macros in the Linux kernel, as well as the kernel-derived
userspace atomics (uatomic) found in liburcu <http://liburcu.org/>
prev parent reply other threads:[~2017-03-21 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:18 Safe to use stdatomic.h? Ben Peart
2017-03-20 20:27 ` Jeff King
2017-03-20 23:22 ` brian m. carlson
2017-03-21 1:59 ` Eric Wong [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170321015948.GC6536@starla \
--to=e@80x24.org \
--cc=Jeff.Hostetler@microsoft.com \
--cc=benpeart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=peartben@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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 NNTP newsgroup(s).