Joel Sherrill created an issue: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/141
## Summary Issue https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5267 resulted in adding code to RTEMS for a default version of \_\__atomic_test_and_set_ being added to RTEMS and multiple BSPs including that file in their build specification. There is now a patch posted for [GCC Issue 118977](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118977). @joel tested this patch and it seems to address the original issue. It is unknown at this point (5 Nov 2025) when this patch will be committed to GCC and to which branches. When it is committed, we need to evaluate what we want to do. Options are: - Add the patch via the RSB - Update the GCC 15 version if the patch is merged to the branch and a new GCC release is made from the 15 branch - Do nothing and carry the current RTEMS solution until 7 is branched and main moves to GCC 16. Setting the milestone to 7.1 so we have a discussion about what to do. ## Steps to reproduce <!-- Pre-set options - milestone --> -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/141 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
