Scary -floop-parallelize-all option doesn't actually do anything except annoy package developers

Bug #1251488 reported by Tim Starling
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Brian Aker

Bug Description

One might think, reading the description of -floop-parallelize-all in the gcc manual, that -floop-parallelize-all will cause automatic parallelization of all loops by enabling a rarely-used, alpha-quality automatic parallelization feature called Graphite. However, this scary prospect is averted because -floop-parallelize-all doesn't actually generate parallel code unless you also specify -ftree-parallelize-loops=N where N is the thread count (that's right, it's fixed at compile time). This is explained at

So all -floop-parallelize-all does is cause the build to fail if libcloog is missing (i.e. bug #1232551), and increase compile time somewhat. I suggest that it be removed.

Related branches

Revision history for this message
Tim Starling (tstarling) wrote :

Note that according to and the linked document is extremely stupid, in that it will add a synchronisation overhead to every execution of every inner loop, even if the loop would complete on a single core in much less time than it takes to do the synchronisation. So there is a good chance that enabling it would actually slow down the application.

Brian Aker (brianaker)
Changed in libmemcached:
milestone: none → 1.0.18
assignee: nobody → Brian Aker (brianaker)
importance: Undecided → Medium
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.