Joseph S. Myers jos...@codesourcery.com writes:
The test gcc.dg/atomic/c11-atomic-exec-5.c will indicate if this is
working correctly for your architecture, as long as your system supports
pthreads (required to run that test). If any of the other
c11-atomic-exec-* tests are failing, you
On Fri, 8 Nov 2013, Andreas Schwab wrote:
Joseph S. Myers jos...@codesourcery.com writes:
The test gcc.dg/atomic/c11-atomic-exec-5.c will indicate if this is
working correctly for your architecture, as long as your system supports
pthreads (required to run that test). If any of the
Joseph S. Myers jos...@codesourcery.com writes:
On Fri, 8 Nov 2013, Andreas Schwab wrote:
Joseph S. Myers jos...@codesourcery.com writes:
The test gcc.dg/atomic/c11-atomic-exec-5.c will indicate if this is
working correctly for your architecture, as long as your system supports
On Fri, 8 Nov 2013, Andreas Schwab wrote:
The tests do not require sync_long_long_runtime.
True, but they require __atomic_store_16, which is generally not
available.
See my comments at
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00894.html - my inclination
is that the code resolving
Architecture maintainers please note: if your architecture supports
floating-point exceptions, you should add a definition of the
TARGET_ATOMIC_ASSIGN_EXPAND_FENV target hook so that they are handled
correctly for C11 atomic compound assignments. This will normally
generate inline code
