Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support C11 atomics on compilers that don't define __GNUC__ if they declare an extension or C11 atomic support. #19840

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Jan 2, 2025

Support C11 atomics on compilers that don't define __GNUC__ if they declare an extension or C11 atomic support.

This fixes:

  • MSVC with /std:c11 /experimental:c11atomics on recent versions now emits atomics
  • Clang with -std=c11 -fgnuc-version=0 now emits atomics
  • Clang and GCC 14 when built with -std=c99 -pedantic-errors will now compile, and not emit atomics

… declare an extension or C11 atomic support.

This fixes:
* MSVC with `/std:c11 /experimental:c11atomics` on recent versions now emits atomics
* Clang with `-std=c11 -fgnuc-version=0` now emits atomics
* Clang and GCC 14 when built with `-std=c99 -pedantic-errors` will now compile, and not emit atomics

PiperOrigin-RevId: 710873174
@copybara-service copybara-service bot changed the title Support C11 atomics on compilers that don't define __GNUC__, and if compiling without atomics, require users to say that's what they want with a define. Support C11 atomics on compilers that don't define __GNUC__ if they declare an extension or C11 atomic support. Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant