Linked by ebasconp on Fri 10th Jun 2011 22:22 UTC
Thread beginning with comment 477064
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: GCC isn't all that great
by Carewolf on Mon 13th Jun 2011 10:30
in reply to "RE[4]: GCC isn't all that great"
Depends on the gcc-version.
I just double-checked: According to info:gcc the most recent version (4.6) has enabled -ftree-vectorize on -O3, but still not -funroll-loops.
Unrolling is only default enabled if you compile with profiling-data that helps the compiler to unroll the correct loops.
RE[6]: GCC isn't all that great
by Neolander on Mon 13th Jun 2011 11:12
in reply to "RE[5]: GCC isn't all that great"
Thanks for the clarification.
I think I can understand the rationale behind that decision : loop unrolling sounds like a rather costly optimization if mindlessly applied to all loops without PGO coming into play. But in this case, where PGO is not used, it indeed reduces the performance of the GCC binary.




Member since:
2010-03-08
Aren't those supposed to be automatically enabled by O2 or O3 ?