--- Comment #7 from tim at klingt dot org 2008-06-15 14:01 ---
i see ... is it possible to enable the complete unroller manually?
from my understanding gcc-4.3 -O3 is the same as -O2 -fgcse-after-reload
-finline-functions -fpredictive-commoning -ftree-vectorize -funswitch-loops ...
usi
--- Comment #6 from pinskia at gcc dot gnu dot org 2008-06-15 13:40 ---
Then it is the complete unroller which means that it is unrolling the loop
fully which is expected from creating the code bloat.
This is not a bug based on that fact.
--
pinskia at gcc dot gnu dot org changed:
--- Comment #5 from tim at klingt dot org 2008-06-15 13:00 ---
i don't think it is related to the vectorizer:
gcc-4.3, -O3 -fno-tree-vectorize: 137088
gcc-4.3, -O3: 137016
gcc-4.3, -O3 -ftree-vectorize: 54640
gcc-4.3, -O3: 54564
--
http:
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-06-15 12:43 ---
Try -O3 -fno-tree-vectorize and report the results. If the code size is back
to normal then this is not a bug. The vectorizer will cause this code bloat on
purpose for speed reasons.
--
pinskia at gcc dot gnu d
--- Comment #3 from pinskia at gcc dot gnu dot org 2008-06-15 12:37 ---
Oh the loop versioning is enabled with the vectorizer which means we could
duplicate the loop a couple of times for aliasing versioning. I bet this is
not really a bug. -O3 is defined to cause this code bloat.
--
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-06-15 12:36 ---
-O3 enables the vectorizer in 4.3 and above so that might be the cause of the
bloat.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
