Gedare Bloom started a new discussion on cpukit/dhrl/dhrl.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_150599 > + memory_order_relaxed > + ) > + ) { > + atomic_store_explicit( > + &ctx->winning_data_ptr, > + (uintptr_t) target_addr, > + memory_order_release > + ); > + } > + > + rtems_barrier_wait( ctx->tail_barrier, RTEMS_NO_TIMEOUT ); > + } > +} > + > +/* Internal Hybrid Barrier Execution */ > +static volatile void *dhrl_fetch_data( I don't think a function return should ever need to be `volatile`. I think this behavior is deprecated and may produce warnings in some compiler configurations. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_150599 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
