Gedare Bloom started a new discussion on cpukit/dhrl/dhrl.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_150607 > + } > + > + rtems_barrier_wait( ctx->tail_barrier, RTEMS_NO_TIMEOUT ); > + } > +} > + > +/* Internal Hybrid Barrier Execution */ > +static volatile void *dhrl_fetch_data( > + struct dhrl_control *ctx, > + volatile void *addr_a, > + volatile void *addr_b > +) > +{ > + volatile void *winning_result; > + > + rtems_mutex_lock( &ctx->mutex ); This mutex is only acquired in this function. Is this function actually called in parallel? I only see sequential execution paths that call to it, so I'm not sure what this mutex is protecting. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_150607 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
