https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113772
--- Comment #9 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to Iain Buclaw from comment #8) > Created attachment 57329 [details] > The quick fix to the lock-free test > > The immediate thing that can be changed is turning the test into a > `__traits(compiles)` one, which would turn the error into a `false` value. I wonder though whether maybe the D compiler could push out some manifest constants into the gcc.builtins module similar to the __GCC_ATOMIC_LLONG_LOCK_FREE macros.
