public inbox for [email protected]
 help / color / mirror / Atom feed
* are volatile and memory barriers necessary for single threaded code?
@ 2020-05-04 16:54 Lorenzo Gabriele
  2020-05-06 13:44 ` Pavel Begunkov
  0 siblings, 1 reply; 3+ messages in thread
From: Lorenzo Gabriele @ 2020-05-04 16:54 UTC (permalink / raw)
  To: io-uring

Hi everyone,
I'm a complete noob so sorry if I'm saying something stupid.
I want to have a liburing-like library for the Scala Native language.
I can't easily use liburing itself because of some limitations of the
language.. So I was rewriting the C code in liburing in Scala Native.
The language is single threaded and, sadly, doesn't support atomic,
nor volatile. I was thinking what are the implications of completely
removing the memory barriers.
Are they needed for something related with multithreading or they are
needed regardless to utilize io_uring?
Thank you very much.
Lorenzo

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-05-18 11:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-05-04 16:54 are volatile and memory barriers necessary for single threaded code? Lorenzo Gabriele
2020-05-06 13:44 ` Pavel Begunkov
2020-05-18 11:31   ` Lorenzo Gabriele

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox