https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107590
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Peter Dimov from comment #7) > I don't see an alignment requirement being mentioned here. I think you misunderstood the alignment issue. There might be no alignment requirement directly on __atomic_test_and_set but if there is a mismatch understanding of alignment of what GCC thinks the alignment of the address should be and what the address really is, then there will be an issue. now that could be still a GCC bug or it can be a bug in the source; usually suballocators providing wrong aligned addresses. But there is not enough information here to figure out what exactly is going wrong. No preprocessed source of the code going wrong. Not even register state or instructions where the segfault is happening (this is would be very useful but not required).
