This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Pessimization from reduce-all-givs and move-all-movables
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Cc: Jerry Quinn <jlquinn at us dot ibm dot com>, gcc at gcc dot gnu dot org
- Date: Wed, 20 Nov 2002 14:03:15 -0800
- Subject: Re: Pessimization from reduce-all-givs and move-all-movables
- References: <E18EO1A-00029F-00@tiamat> <3DDBED2A.20909@moene.indiv.nluug.nl>
Toon Moene <toon@moene.indiv.nluug.nl> writes:
> Jerry Quinn wrote:
>
>> Without -fmove-all-movables -freduce-all-givs, performance improves to
>> 1048 Kpos/sec, a 7% difference.
>
> This wouldn't surprise me. Between when I introduced those flags (in
> 1997) and now we gathered quite some information on them. It turns
> out they're mostly useful for Fortran code (subroutines) with rank-n
> dummy arguments where n>1. Because this situation is so common in
> Fortran code, these options are enabled by default when invoking g77.
Can we come up with an algorithm that can tell whether these
optimizations will improve code or not, and enable them only where
they'll help?
zw