comp.programming.threads

• Thread Index

---

• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: semi-timely interrupt
  • From: Arnold Hendriks
• Re: Dedicated lock-free group
  • From: Dmitriy Vyukov
• Re: Dedicated lock-free group
  • From: Thomas Richter
• Re: Dedicated lock-free group
  • From: Dmitriy Vyukov
• Re: Dedicated lock-free group
  • From: Torsten Robitzki
• Re: what is Demon Thread.
  • From: David Schwartz
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Joe Seigh
• Re: multithreading
  • From: SPX2
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Ian Collins
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Elcaro Nosille
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Joe Seigh
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Joe Seigh
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Steve Watt
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Dedicated lock-free group
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Ian Collins
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: multithreading
  • From: David Hopwood
• Re: perl multithreading
  • From: szabolcs . ferenczi
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Elcaro Nosille
• Re: perl multithreading
  • From: SPX2
• Re: perl multithreading
  • From: szabolcs . ferenczi
• Re: perl multithreading
  • From: Joe Seigh
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Joe Seigh
• Re: perl multithreading
  • From: SPX2
• Re: perl multithreading
  • From: SPX2
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• printing thread specific data of a thread in a corefile
  • From: linux_bp
• Re: perl multithreading
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Dmitriy Vyukov
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: semi-timely interrupt
  • From: Andy
• Re: semi-timely interrupt
  • From: David Hopwood
• Re: Problem with _beginthread function
  • From: David Hopwood
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: David Hopwood
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Ulrich Kroemer
• Re: Problem with _beginthread function
  • From: Mikep
• Re: perl multithreading
  • From: Joe Seigh
• Re: Problem with _beginthread function
  • From: abinash . pati
• what is Demon Thread.
  • From: abinash . pati
• Re: Problem with _beginthread function
  • From: Dmitriy Vyukov
• Problem with _beginthread function
  • From: Alex
• Re: Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Elcaro Nosille
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: Chris Thomasson
• Global Lock-Free Proxy Collector Anchor Scheme...
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: semi-timely interrupt
  • From: Andy
• Re: semi-timely interrupt
  • From: David Hopwood
• Re: semi-timely interrupt
  • From: David Hopwood
• Re: perl multithreading
  • From: szabolcs . ferenczi
• Re: re-entrent java native function
  • From: David Hopwood
• Re: perl multithreading
  • From: szabolcs . ferenczi
• Re: semi-timely interrupt
  • From: David Schwartz
• Re: Association of lock with condvar, basic POSIX question
  • From: David Schwartz
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: David Hopwood
• Re: perl multithreading
  • From: SPX2
• Re: perl multithreading
  • From: Joe Seigh
• perl multithreading
  • From: SPX2
• Re: semi-timely interrupt
  • From: Andy
• Re: semi-timely interrupt
  • From: Frank Cusack
• Re: semi-timely interrupt
  • From: Eric Sosman
• Re: semi-timely interrupt
  • From: Andy
• Re: Association of lock with condvar, basic POSIX question
  • From: Steve Watt
• Re: semi-timely interrupt
  • From: Steve Watt
• Re: re-entrent java native function
  • From: Andy
• Re: FIFO problem: deadlock when deleting
  • From: Marcin 'Qrczak' Kowalczyk
• Re: FIFO problem: deadlock when deleting
  • From: Frank Cusack
• Re: FIFO problem: deadlock when deleting
  • From: hexa
• Re: semi-timely interrupt
  • From: David Schwartz
• Re: semi-timely interrupt
  • From: Dmitriy Vyukov
• Re: semi-timely interrupt
  • From: Frank Cusack
• Re: semi-timely interrupt
  • From: algorimancer
• Custom Software Development
  • From: VB
• semi-timely interrupt
  • From: Andy
• Re: FIFO problem: deadlock when deleting
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: DanielHolley1982
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: DanielHolley1982
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: pthread compliance library
  • From: Chris Friesen
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: David Hopwood
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Dmitriy Vyukov
• Re: Brief vZOOM Licensing Model Intro...
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: Association of lock with condvar, basic POSIX question
  • From: Alexander Terekhov
• Re: Association of lock with condvar, basic POSIX question
  • From: Ian Collins
• Re: Association of lock with condvar, basic POSIX question
  • From: David Hopwood
• Re: Association of lock with condvar, basic POSIX question
  • From: David Schwartz
• Re: Association of lock with condvar, basic POSIX question
  • From: Ian Collins
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Association of lock with condvar, basic POSIX question
  • From: David Schwartz
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: rfistman@xxxxxxxxx
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: Scaleable multi-threaded allocator solutions for embedded systems with NO heap...
  • From: Chris Thomasson
• Re: Scaleable multi-threaded allocator solutions for embedded systems with NO heap...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: Scaleable multi-threaded allocator solutions for embedded systems with NO heap...
  • From: Chris Thomasson
• Scaleable multi-threaded allocator solutions for embedded systems with NO heap...
  • From: Chris Thomasson
• Re: Does 32 bits value assignment needs locking operation
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: Does 32 bits value assignment needs locking operation
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Andy
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: David Hopwood
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: David Hopwood
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Dmitriy Vyukov
• Re: FIFO problem: deadlock when deleting
  • From: Joe Seigh
• Re: lock-free node allocator for fifo-queues
  • From: Andy
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: mutexes 101 (multi-cpu)
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Andy
• SetPriority(int) Test Driven
  • From: Green
• Re: mutexes 101 (multi-cpu)
  • From: Marcin 'Qrczak' Kowalczyk
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• pthread compliance library
  • From: Frank Cusack
• Re: mutexes 101 (multi-cpu)
  • From: Frank Cusack
• Re: mutexes 101 (multi-cpu)
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Dmitriy Vyukov
• Re: Static functions - independence in threads
  • From: algorimancer
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Dmitriy Vyukov
• Re: mutexes 101 (multi-cpu)
  • From: Casper H . S . Dik
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: Static functions - independence in threads
  • From: John Dallman
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: mutexes 101 (multi-cpu)
  • From: Frank Cusack
• Re: Static functions - independence in threads
  • From: robertwessel2@xxxxxxxxx
• Re: Static functions - independence in threads
  • From: Marcin 'Qrczak' Kowalczyk
• Re: atomic increment and fetch on intel ia32
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: Frank Cusack
• Re: FIFO problem: deadlock when deleting
  • From: Marcin 'Qrczak' Kowalczyk
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Chris Thomasson
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: Static functions - independence in threads
  • From: algorimancer
• Re: Static functions - independence in threads
  • From: John Dallman
• Re: Static functions - independence in threads
  • From: John Dallman
• Re: Static functions - independence in threads
  • From: algorimancer
• Re: Static functions - independence in threads
  • From: Sergei Organov
• Re: Static functions - independence in threads
  • From: algorimancer
• Re: FIFO problem: deadlock when deleting
  • From: hexa
• Re: Static functions - independence in threads
  • From: hexa
• Re: FIFO problem: deadlock when deleting
  • From: hexa
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: David Tiktin
• Re: Static functions - independence in threads
  • From: Dmitriy Vyukov
• Static functions - independence in threads
  • From: algorimancer
• MPMC Unbounded FIFO Queue w/ 1 CAS/Operation. No jokes.
  • From: Dmitriy Vyukov
• Re: FIFO problem: deadlock when deleting
  • From: TvN
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: FIFO problem: deadlock when deleting
  • From: Joe Seigh
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Dmitriy Vyukov
• Re: Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Dmitriy Vyukov
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Anthony Williams
• Re: FIFO problem: deadlock when deleting
  • From: Torsten Robitzki
• Re: FIFO problem: deadlock when deleting
  • From: hexa
• FIFO problem: deadlock when deleting
  • From: hexa
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: atomic increment and fetch on intel ia32
  • From: Joe Seigh
• Lock-Free Fast-Pathed Static Initialization On x86-Windows...
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: atomic increment and fetch on intel ia32
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: atomic increment and fetch on intel ia32
  • From: robertwessel2@xxxxxxxxx
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Transforming single-thread malloc impls into lock-free multi-thread ones...
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: atomic increment and fetch on intel ia32
  • From: Casper H . S . Dik
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: atomic increment and fetch on intel ia32
  • From: Andy
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: David Tiktin
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: David Tiktin
• Re: Does 32 bits value assignment needs locking operation
  • From: Casper H . S . Dik
• Re: Recursive locks
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• Re: atomic increment and fetch on intel ia32
  • From: Andy
• Re: atomic increment and fetch on intel ia32
  • From: Andy
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: atomic increment and fetch on intel ia32
  • From: Dmitriy Vyukov
• Re: should I declare them volatile
  • From: David Schwartz
• Re: atomic increment and fetch on intel ia32
  • From: robertwessel2@xxxxxxxxx
• Re: atomic increment and fetch on intel ia32
  • From: robertwessel2@xxxxxxxxx
• Re: atomic increment and fetch on intel ia32
  • From: Joe Seigh
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Joe Seigh
• Re: Does 32 bits value assignment needs locking operation
  • From: Chris Thomasson
• Re: Does 32 bits value assignment needs locking operation
  • From: Chris Thomasson
• Re: Does 32 bits value assignment needs locking operation
  • From: Chris Thomasson
• Re: DDJ Article: Statically Initializable C++ Mutexes
  • From: Chris Thomasson
• Re: mutexes 101 (multi-cpu)
  • From: Chris Thomasson
• Re: should I declare them volatile
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: Recursive locks
  • From: Casper H . S . Dik
• Re: mutexes 101 (multi-cpu)
  • From: Frank Cusack
• Recursive locks
  • From: Amit
• Recursive locks
  • From: Amit
• Re: Thread debugging utilities.
  • From: Amit
• Re: How to caputre stack trace in production environment
  • From: Amit
• Re: How to caputre stack trace in production environment
  • From: Amit
• atomic increment and fetch on intel ia32
  • From: Andy
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• DDJ Article: Statically Initializable C++ Mutexes
  • From: David Tiktin
• Re: Does 32 bits value assignment needs locking operation
  • From: Casper H . S . Dik
• Re: Does 32 bits value assignment needs locking operation
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: should I declare them volatile
  • From: Markus Elfring
• Re: How to caputre stack trace in production environment
  • From: Sheth Raxit
• Re: Does 32 bits value assignment needs locking operation
  • From: Markus Elfring
• Re: Does 32 bits value assignment needs locking operation
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: mutexes 101 (multi-cpu)
  • From: Casper H . S . Dik
• Re: should I declare them volatile
  • From: adebaene
• Re: Does 32 bits value assignment needs locking operation
  • From: lxconan
• Re: Does 32 bits value assignment needs locking operation
  • From: David Schwartz
• Does 32 bits value assignment needs locking operation
  • From: lxconan
• Re: mutexes 101 (multi-cpu)
  • From: David Schwartz
• Re: mutexes 101 (multi-cpu)
  • From: Chris Thomasson
• Re: should I declare them volatile
  • From: Chris Thomasson
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• Re: mutexes 101 (multi-cpu)
  • From: Frank Cusack
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• Re: mutexes 101 (multi-cpu)
  • From: Torsten Robitzki
• Re: mutexes 101 (multi-cpu)
  • From: Andy
• mutexes 101 (multi-cpu)
  • From: Andy
• Re: should I declare them volatile
  • From: Markus Elfring
• Re: should I declare them volatile
  • From: adebaene
• Re: should I declare them volatile
  • From: Chris Thomasson
• Re: Thread debugging utilities.
  • From: mliptak
• Re: should I declare them volatile
  • From: Joe Seigh
• Re: should I declare them volatile
  • From: Chris Thomasson
• Re: should I declare them volatile
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Thread debugging utilities.
  • From: Ian Collins
• Re: should I declare them volatile
  • From: David Schwartz
• should I declare them volatile
  • From: junky_fellow@xxxxxxxxxxx
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: How to caputre stack trace in production environment
  • From: Logan Shaw
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Worker Threads
  • From: David Schwartz
• Thread debugging utilities.
  • From: Amit
• How to caputre stack trace in production environment
  • From: Amit
• Worker Threads
  • From: Amit
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: You CAN test threaded code
  • From: szabolcs . ferenczi
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: Dmitriy Vyukov
• Re: x86 xadd w/o lock prefix
  • From: Chris Thomasson
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: David Hopwood
• Re: Thread-safe Queue on Win32
  • From: David Schwartz
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: frege
• Re: Strong vs. Normal Thread Safety.
  • From: frege
• Re: Strong vs. Normal Thread Safety.
  • From: frege
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: double-word-cas on x86-64
  • From: Dmitriy Vyukov
• Re: double-word-cas on x86-64
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: double-word-cas on x86-64
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• double-word-cas on x86-64
  • From: Dmitriy Vyukov
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: Thread-safe Queue on Win32
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Thread-safe Queue on Win32
  • From: Joe Seigh
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Thread-safe Queue on Win32
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: llothar
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: Gianni Mariani
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Urgent : How to know context switch has occurred or not using VC++
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: Joe Seigh
• Urgent : How to know context switch has occurred or not using VC++
  • From: Abhi
• Re: Strong vs. Normal Thread Safety.
  • From: Dmitriy Vyukov
• Re: lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: frege
• Re: Thread-safe Queue on Win32
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: atomically thread-safe
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: lock-free node allocator for fifo-queues
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• lock-free node allocator for fifo-queues
  • From: Dmitriy Vyukov
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: Thread-safe Queue on Win32
  • From: Marcel Müller
• Re: Strong vs. Normal Thread Safety
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: You CAN test threaded code
  • From: Gianni Mariani
• Re: You CAN test threaded code
  • From: Eric Sosman
• Re: Developing a Standard C PDR API for This Group.
  • From: Joe Seigh
• You CAN test threaded code
  • From: Gianni Mariani
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Thread-safe Queue on Win32
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Developing a Standard C PDR API for This Group.
  • From: Chris Thomasson
• Re: Developing a Standard C PDR API for This Group.
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: synchronizing 3 threads
  • From: none
• Re: Strong vs. Normal Thread Safety
  • From: Markus Elfring
• Re: Thread-safe Queue on Win32
  • From: Joe Seigh
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: atomically thread-safe
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: David Hopwood
• Re: Strong vs. Normal Thread Safety.
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Peter Dimov
• atomically thread-safe
  • From: Joe Seigh
• Re: Strong vs. Normal Thread Safety.
  • From: Gianni Mariani
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Lock-Free Datastructures not ready for practical use
  • From: Chris Thomasson
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Strong vs. Normal Thread Safety.
  • From: Gianni Mariani
• Strong vs. Normal Thread Safety.
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: x86 xadd w/o lock prefix
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: How do I get my threaded program to run on both CPU's of my Opteron?
  • From: Markus Elfring
• Re: Question about vZOOM
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: How do I get my threaded program to run on both CPU's of my Opteron?
  • From: Jeff
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Question about vZOOM
  • From: Joe Seigh
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Question about vZOOM
  • From: Joe Seigh
• Re: Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Question about vZOOM
  • From: Joe Seigh
• Re: Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Resolution...
  • From: Steve Watt
• Re: Thread-safe Queue on Win32
  • From: Joe Seigh
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: How do I get my threaded program to run on both CPU's of my Opteron?
  • From: David Schwartz
• Re: Sighandler/Threads: NPTL working, linuxthreads not
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Thread-safe Queue on Win32
  • From: Roman Perepelitsa
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Sighandler/Threads: NPTL working, linuxthreads not
  • From: Martin Vuille
• Re: Multi-Platform portability using threads: autotools
  • From: Marcin 'Qrczak' Kowalczyk
• Multi-Platform portability using threads: autotools
  • From: Johannes Bauer
• Re: Sighandler/Threads: NPTL working, linuxthreads not
  • From: llothar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Gil Hamilton
• Re: Thread-safe Queue on Win32
  • From: Marcel Müller
• Re: Sighandler/Threads: NPTL working, linuxthreads not
  • From: Johannes Bauer
• Re: Sighandler/Threads: NPTL working, linuxthreads not
  • From: Marcin 'Qrczak' Kowalczyk
• Sighandler/Threads: NPTL working, linuxthreads not
  • From: Johannes Bauer
• Thread-safe Queue on Win32
  • From: Roman.Perepelitsa@xxxxxxxxx
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: can someone explain memory barriers (singletons)
  • From: Holger Hoffstaette
• How do I get my threaded program to run on both CPU's of my Opteron?
  • From: Jeff
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Brief vZOOM Licensing Model Intro...
  • From: Dmitriy Vyukov
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: can someone explain memory barriers (singletons)
  • From: Chris Thomasson
• Re: C++ threads, sockets
  • From: Michael K. O'Neill
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: x86 xadd w/o lock prefix
  • From: Chris Thomasson
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: kunniu
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: x86 xadd w/o lock prefix
  • From: David Schwartz
• can someone explain memory barriers (singletons)
  • From: Andy
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: x86 xadd w/o lock prefix
  • From: Chris Thomasson
• Re: Question about vZOOM
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: David Schwartz
• Question about vZOOM
  • From: Dmitriy Vyukov
• Re: Brief vZOOM Licensing Model Intro...
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Resolution...
  • From: tclegg@xxxxxxxx
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Resolution...
  • From: Christoph Bartoschek
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: kunniu
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: Resolution...
  • From: tclegg@xxxxxxxx
• Re: Resolution...
  • From: David Schwartz
• Re: Resolution...
  • From: tclegg@xxxxxxxx
• Re: Resolution...
  • From: David Schwartz
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: David Schwartz
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: x86 xadd w/o lock prefix
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: thread-safety for adjacent data fields
  • From: dick.dunbar
• Re: Lock-free proxy algorithm
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: Barrier using monitors
  • From: Leo
• Re: re-entrent java native function
  • From: Andy
• Re: Barrier using monitors
  • From: Joe Seigh
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: kunniu
• Re: thread-safety for adjacent data fields
  • From: Markus Elfring
• Re: x86 xadd w/o lock prefix
  • From: Marcel Müller
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Can I implement a timer within a thread without a blocking wait?
  • From: Bin Chen
• Re: Barrier using monitors
  • From: kunniu
• Brief vZOOM Licensing Model Intro...
  • From: Chris Thomasson
• Re: Lock-free proxy algorithm
  • From: Dmitriy Vyukov
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Memory leaks with pthread
  • From: Paul Pluzhnikov
• Barrier using monitors
  • From: Leo
• Re: re-entrent java native function
  • From: Andy
• Re: Here we go again: SpinLocks, Mutex, Shared Memory :(
  • From: Chris Thomasson
• Re: x86 xadd w/o lock prefix
  • From: Chris Thomasson
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• Re: re-entrent java native function
  • From: Andy
• Memory leaks with pthread
  • From: tclegg@xxxxxxxx
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Marcin 'Qrczak' Kowalczyk
• Re: thread-safety for adjacent data fields
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Peter Dimov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Peter Dimov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Should shared _r libraries depend on threading library?
  • From: David Hopwood
• Re: thread-safety for adjacent data fields
  • From: Markus Elfring
• Re: re-entrent java native function
  • From: David Hopwood
• Re: re-entrent java native function
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: x86 xadd w/o lock prefix
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Peter Dimov
• Resolution...
  • From: tclegg@xxxxxxxx
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Should shared _r libraries depend on threading library?
  • From: Paul Pluzhnikov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: re-entrent java native function
  • From: David Hopwood
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: malc
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Peter Dimov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Hopwood
• Re: re-entrent java native function
  • From: Andy
• Re: re-entrent java native function
  • From: Andy
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Thomas Richter
• Re: x86 xadd w/o lock prefix
  • From: Marcel Mu"ller
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Gil Hamilton
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: rfistman@xxxxxxxxx
• x86 xadd w/o lock prefix
  • From: Dmitriy Vyukov
• Re: Should shared _r libraries depend on threading library?
  • From: Peter
• Re: experimental 100% lock-free bounded pointer queue code...
  • From: Dmitriy Vyukov
• Can I implement a timer within a thread without a blocking wait?
  • From: kunniu
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Barry Kelly
• Re: Should shared _r libraries depend on threading library?
  • From: Paul Pluzhnikov
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Re: re-entrent java native function
  • From: Chris Thomasson
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: David Schwartz
• Re: experimental 100% lock-free bounded pointer queue code...
  • From: Chris Thomasson
• Re: linux/pthread: beginners question about thread creation...
  • From: Thomas Richter
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Thomas Richter
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: Barry Kelly
• Re: Boolean Buyers Beware ... AIX compiler bug --- PMR 26241,756
  • From: dick.dunbar
• Behavior appears to be related to the kernel (Xubuntu 7.04 vs. Ubuntu 6.10) or the installation...
  • From: tclegg@xxxxxxxx
• Re: Should shared _r libraries depend on threading library?
  • From: David Schwartz

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

newsgroups.derkeiler.com  > Archive  > Comp  > comp.programming.threads  > 2007-05