Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #443
| From | Alexander Terekhov <terekhov@web.de> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | Re: Interlocked operations, volatile |
| Date | 2011-07-14 23:05 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <4E1F5A20.2568A5DD@web.de> (permalink) |
| References | (2 earlier) <c66aeae2-aac5-40b0-ba90-8836c6c5cb45@m10g2000yqd.googlegroups.com> <6f742fb4-cb39-4b56-b062-4eeb1e51ebdb@h25g2000prf.googlegroups.com> <3806a754-4ec5-4e71-be4d-318db1760557@u24g2000prn.googlegroups.com> <7232157d-7a0a-43e6-8462-dca56a861dd0@t9g2000vbs.googlegroups.com> <aa6c3fde-aef6-413d-b18e-585fff1379c8@j14g2000prn.googlegroups.com> |
David Schwartz wrote: > > On Jul 14, 8:52 am, Andrew Che <libera.ven...@gmail.com> wrote: > > > Couldn't You give an (C++) example that demonstrates difference > > between: > > 1) concurrent write with locks and read WITH locks > > 2) concurrent write with locks and read WITHOUT locks > > > I mean I would like to see a program that prints something like "a" in > > case 1) and "aaaa" in case 2) because races are. > > Not really. C++ provides no way to have concurrent flows of execution. Upcomming C++11 does provide threading... > And whatever scheme we use to have concurrent flows of execution will > also include rules that prohibit concurrent write and read without > locks. ... and atomics (concurrent write and read without locks allowed). regards, alexander.
Back to comp.programming.threads | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-13 09:43 -0700
Re: Interlocked operations, volatile Alexander Terekhov <terekhov@web.de> - 2011-07-13 20:03 +0200
Re: Interlocked operations, volatile David Schwartz <davids@webmaster.com> - 2011-07-13 15:24 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:13 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:17 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:37 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:41 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:44 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:31 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:52 -0700
Re: Interlocked operations, volatile David Schwartz <davids@webmaster.com> - 2011-07-14 03:06 -0700
Re: Interlocked operations, volatile David Schwartz <davids@webmaster.com> - 2011-07-14 06:16 -0700
Re: Interlocked operations, volatile Alexander Terekhov <terekhov@web.de> - 2011-07-14 17:20 +0200
Re: Interlocked operations, volatile David Schwartz <davids@webmaster.com> - 2011-07-14 09:19 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 08:52 -0700
Re: Interlocked operations, volatile David Schwartz <davids@webmaster.com> - 2011-07-14 10:51 -0700
Re: Interlocked operations, volatile Alexander Terekhov <terekhov@web.de> - 2011-07-14 23:05 +0200
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 08:49 -0700
Re: Interlocked operations, volatile Andrew Che <libera.ventis@gmail.com> - 2011-07-14 00:48 -0700
Re: Interlocked operations, volatile frege <gottlobfrege@gmail.com> - 2011-07-20 22:13 -0700
csiph-web