On Fri, 2006-11-10 at 13:31 -0800, Mike Stump wrote: > On Nov 10, 2006, at 12:46 PM, H. J. Lu wrote: > > Will use C++ help or hurt compiler parallelism? Does it really matter? > > I'm not an expert, but, in the simple world I want, I want it to not > matter in the least. For the people writing most code in the > compiler, I want clear simple rules for them to follow. > > For example, google uses mapreduce http://labs.google.com/papers/ > mapreduce.html as a primitive, and there are a few experts that > manage that code, and everyone else just mindlessly uses it. The > rules are explained to them, and they just follow the rules and it > just works. No locking, no atomic, no volatile, no cleaver lock free > code, no algorithmic changes (other than decomposing into isolated > composable parts) . I'd like something similar for us.
What parts could be done in parallel besides things that can be done by make -j80? I would guess that certain tree transformations could be run in parallel. Do threads help for io-bound apps? Thanks, Sohail
