|
|
Install an optimized BIND 9.2.3Beta
I was about to reply stating that -O3 does not unroll loops. But I decided to double check this first through the gcc man page on 10.2.3. To my surprise, -floop-optimize is enabled for all -0x (excluding x=0). However, it is not clear if -O3 actually unrolls loops by asserting this flag. Man page states:
Optionally? Under the versions of Linux that I've used, loop unrolling has to be explicitly enabled even if you compile with -O3. What is the case on OS X? My guess is that loop unrolling will not take place unless explicitly specified since -floop-optimize description uses the word "optional". Options typically need to be stated/selected. Anyone agree, disagree, prove, or disprove? If -floop-optimize does not unroll loops, then the stuff above about loop unrolling is moot since no unrolling ever took place.
Install an optimized BIND 9.2.3Beta
-O3 will unroll loops, but will determine by heuristics which ones are worth unrolling. To unroll all loops you need a separate flag. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|