Wayne Thornton commented on a discussion on cpukit/dhrl/dhrl.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_148405 > + } > + > + // Initialize Worker A > + sc = rtems_task_create( > + rtems_build_name( 'D', 'H', 'R', 'A' ), > + priority, > + RTEMS_MINIMUM_STACK_SIZE, > + RTEMS_DEFAULT_MODES, > + RTEMS_DEFAULT_ATTRIBUTES, > + &dhrl_worker_a_id > + ); > + if ( sc != RTEMS_SUCCESSFUL ) { > + return sc; > + } > + > + CPU_ZERO( &cpuset ); I was thinking about it, and while my previous answer addressed the question literally, the technical reality is that I should provide a pre-processor macro RTEMS_SMP to define a compile-time fence in both the header and the implementation file. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_148405 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
