git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Safe to use stdatomic.h?

From
EWEric Wong <e@80x24.org>
Date
Mar 21, 2017, 01:59 UTC
Message-ID
<20170321015948.GC6536@starla>
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/>

Previous: brian m. carlson
Message 4 of 4 in “Safe to use stdatomic.h?”
  1. Ben PeartMar 20, 2017
  2. Jeff KingMar 20, 2017
  3. brian m. carlsonMar 20, 2017
  4. Eric WongMar 21, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.