This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [patch, fortran] More control over front end optimization
- From: Mikael Morin <mikael dot morin at sfr dot fr>
- To: fortran at gcc dot gnu dot org
- Cc: Daniel Kraft <d at domob dot eu>, Thomas Koenig <tkoenig at netcologne dot de>, "gcc-patches" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 7 Apr 2011 22:35:00 +0200
- Subject: Re: [patch, fortran] More control over front end optimization
- References: <4D9E1168.50908@netcologne.de> <4D9E1596.9020707@domob.eu>
Hello,
On Thursday 07 April 2011 21:50:46 Daniel Kraft wrote:
> Ok. Just my opinion (as non-native-speaker), though:
+@item -ffrontend-optimize
+@opindex @code{frontend-optimize}
+@cindex Front-end optimization
+This option performs front-end optimization, based on the Fortran parse
+tree. Enabled by default by any @option{-O} option. It can
+be deselcted by specifying @option{-fno-frontend-optimize}.
@end table
s/deselcted/deselected/ ?
I think you are not specific enough about frontend optimizations.
frontend optimization consists of:
* the trim/trim_len stuff
* the duplicate function call removal stuff
This is documented nowhere ( but the C source ;-) ) as far as I know.
> The code looks good to me.
Mikael