Central | Draft: spec: Add msg broadcast non-atomicity note to doc (!14)

Martin Werner (@martinerikwerner) gitlab at rtems.org
Sat Oct 18 20:26:05 UTC 2025



Martin Werner created a merge request: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/14

Project:Branches: martinerikwerner/rtems-central:msg-broadcast-is-non-atomic to rtems/prequal/rtems-central:main
Author:   Martin Werner




## Summary

spec: Add msg broadcast non-atomicity note to doc

rtems_message_queue_broadcast() may, under certain circumstances, copy
the message to tasks which were not waiting on the message queue when
the broadcast started, and may copy the message multiple times to the
same task.

This behaviour is, based on discussion in
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/4804, something that
might not change in the short term.

Expose the note regarding this behaviour that already exists in
spec/rtems/message/req/broadcast.yml to make it visible in the
user-facing interface documentation, with the following modifications:

* Remove the "Currently" wording.
* Avoid barrier-specific glossary references since these do not work in
  rtems/*/if/*.yml files (see #6).
* Use "this directive" instead of "${broadcast:/name}" when referring to
  itself.


<!-- Default settings, if it is a dropdown it will set after submission -->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/14
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251018/7388695a/attachment.htm>


More information about the bugs mailing list