mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2026-08-25 20:49:52 +08:00
Pavel Pisa
dfcec5595f
The single write to memory or ioport output are mostly atomic operations already. The proper memory synchronization barrier should be used around them to guarantee ordering (sync or eieio on PowerPC for example) but because I have not found settable portable primitive only compiler barrier is used. It should be enough on x86 because the externally visible order should be/is guaranteed to be preserved on x86 architecture.
This is the Real-Time Executive for Multiprocessing Systems (RTEMS). The version number for this software is indicated in the VERSION file. See the documentation manuals in doc/ with daily builds available online at http://rtems.org/onlinedocs/doc-current/share/rtems/html/ and released builds at http://www.rtems.org/onlinedocs/releases/ for information on building, installing, and using RTEMS. The INSTALL file tells you to come back here. See the RTEMS Wiki at http://devel.rtems.org for community knowledge and tutorials. RTEMS Doxygen available at http://www.rtems.org/onlinedocs/doxygen/cpukit/html The RTEMS Project maintains mailing lists which are used for most discussions: * For general-purpose questions related to using RTEMS, use the rtems-users ml: https://lists.rtems.org/mailman/listinfo/users * For questions and discussion related to development of RTEMS, use the rtems-devel ml: https://lists.rtems.org/mailman/listinfo/devel See https://devel.rtems.org/ to view existing or file a new issue report ticket.