Zdenek Dvorak <[EMAIL PROTECTED]>:
> Hello,
>
> > Giv optimizations are just features which not
> > implemented yet in the new loop unroller, so I
think
> > put it in bugzilla is not appropriate.
>
> it most definitely is appropriate. This is a
performance
Hello,
> Giv optimizations are just features which not
> implemented yet in the new loop unroller, so I think
> put it in bugzilla is not appropriate.
it most definitely is appropriate. This is a performance
regression. Even if it would not be, feature requests
can be put to Bugzi
On Feb 28, 2005, at 10:18 PM, Canqun Yang wrote:
Giv optimizations are just features which not
implemented yet in the new loop unroller, so I think
put it in bugzilla is not appropriate.
Bugzilla should be used more than just normal bugs but
also enhancements.
I test 171.swim on IA64 system with
analysis (very
simple one), loop unrolling (the old one), loop arrays
pre-fetching, and giv optimizations, it costs just
9.1s (28s for GCC-4.0.0) to execute the train mode of
171.swim. But, apply those changes on current GCC-
4.0.0 (the old loop unroller was removed), it costs
13.4 to execute
On Feb 28, 2005 02:35 PM, Canqun Yang <[EMAIL PROTECTED]> wrote:
> Hi, all
>
> The new loop unroller causes performance degradation
> due to the unimplemented giv (general induction
> variable) optimizations.
>
> When will it be implemented?
Will you be more specific so we can have a clue w
Hi, all
The new loop unroller causes performance degradation
due to the unimplemented giv (general induction
variable) optimizations.
When will it be implemented?
Canqun Yang
Creative Compiler Research Group.
National University of Defense Technology, China.
