Using C/Pthreads: do shared variables need to be volatile?

by

As long as you are using locks to control access to the variable, you do not need volatile on it. In fact, if you’re putting volatile on any variable you’re probably already wrong.

https://software.intel.com/en-us/blogs/2007/11/30/volatile-almost-useless-for-multi-threaded-programming/

More Related Contents:

  1. Undefined reference to pthread_create in Linux
  2. When the main thread exits, do other threads also exit?
  3. Kill Thread in Pthread Library
  4. Is it possible to determine the thread holding a mutex?
  5. Can I get Unix’s pthread.h to compile in Windows?
  6. Pthread Run a thread right after it’s creation
  7. How do you query a pthread to see if it is still running?
  8. Linux/POSIX equivalent for Win32’s CreateEvent, SetEvent, WaitForSingleObject
  9. Which thread handles the signal?
  10. Unexpected output in a multithreaded program
  11. Please explain the following parallel code template
  12. POSIX threads and signals
  13. How do I start threads in plain C?
  14. sem_init on OS X
  15. Wake up thread blocked on accept() call
  16. Signal handling with multiple threads in Linux
  17. POSIX API call to list all the pthreads running in a process
  18. How to return a value from pthread threads in C?
  19. Is it OK to call pthread_exit from main?
  20. How to signal select() to return immediately?
  21. Interprocess mutex with pthreads
  22. fork and existing threads?
  23. Is accept() thread-safe?
  24. Does pthread_mutex_lock contains memory fence instruction? [duplicate]
  25. Is it possible to access/update the child thread’s resource from parent thread?
  26. Multiple threads and CPU cache
  27. How to set up pthreads on windows?
  28. Pthreads vs. OpenMP
  29. Atomically increment two integers with CAS
  30. Does “volatile” guarantee anything at all in portable C code for multi-core systems?

Leave a Comment