Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #1800
| From | Anthony Williams <anthony.ajw@gmail.com> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | Re: forcing the compiler to reload from memory with c++0x |
| References | (13 earlier) <iifb30$9d3$1@news.eternal-september.org> <99c58954-6434-4135-b90a-da60dc1d865d@i14g2000prm.googlegroups.com> <iifuoj$1j3$1@news.eternal-september.org> <d1258777-65bc-4ea1-8494-70e8a6d00d98@y35g2000prc.googlegroups.com> <92f9e621-9df2-4ce4-bfa5-64f29924112b@z3g2000prz.googlegroups.com> |
| Date | 2011-02-04 09:21 +0000 |
| Message-ID | <87fws49mtr.fsf@justsoftwaresolutions.co.uk> (permalink) |
| Organization | CNNTP |
Joshua Maurice <joshuamaurice@gmail.com> writes:
> Well, specifically, the compiler may optimize this:
> atomic<int> a_int;
> //...
> int tmp = a_int.get(relaxed);
> do_something(tmp);
> for ( ; ! a_int.get(relaxed) ; )
> {
> }
>
> to this:
> atomic<int> a_int;
> //...
> int tmp = a_int.get(relaxed);
> do_something(tmp);
> for ( ; ! tmp ; tmp = a_int.get(relaxed))
> {
> }
Correct (assuming that do_something doesn't introduce any memory
ordering constraints). Then, if it can prove that !tmp is false
(i.e. tmp is non-zero) then the loop will never execute, so it can omit
the whole loop.
> But it cannot optimize it to this:
> atomic<int> a_int;
> //...
> int tmp = a_int.get(relaxed);
> do_something(tmp);
> for ( ; ! tmp ; )
> {
> }
Correct.
> It's perfectly fine to remove a finite number of loads (assuming it
> doesn't violate other visibility requirements) as the first rewrite
> does, but it cannot remove /all/ loads from a loop like the second
> rewrite, because that would violate the "become visible in a
> 'reasonable' [read: finite] amount of time" guarantee.
Correct.
Anthony
--
Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/
just::thread C++0x thread library http://www.stdthread.co.uk
Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk
15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976
Back to comp.programming.threads | Previous | Next — Previous in thread | Next in thread | Find similar
Re: forcing the compiler to reload from memory with c++0x Andy Venikov <swojchelowek@gmail.com> - 2011-02-03 23:19 -0500
Re: forcing the compiler to reload from memory with c++0x Andy Venikov <swojchelowek@gmail.com> - 2011-02-06 23:17 -0500
Re: forcing the compiler to reload from memory with c++0x Anthony Williams <anthony.ajw@gmail.com> - 2011-02-04 09:21 +0000
Re: forcing the compiler to reload from memory with c++0x Anthony Williams <anthony.ajw@gmail.com> - 2011-02-04 08:42 +0000
Re: forcing the compiler to reload from memory with c++0x Joshua Maurice <joshuamaurice@gmail.com> - 2011-02-03 22:45 -0800
Re: forcing the compiler to reload from memory with c++0x Joshua Maurice <joshuamaurice@gmail.com> - 2011-02-04 00:28 -0800
csiph-web