This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [gfortran,patch] PR fortran/28163: Don't call library function for string copying
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: Bernhard Fischer <rep dot nop at aon dot at>, gfortran <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 25 Jun 2006 08:48:33 -0700
- Subject: Re: [gfortran,patch] PR fortran/28163: Don't call library function for string copying
- References: <449E8545.3090009@gmail.com> <20060625125929.GN5379@aon.at> <449EAFC3.9060606@gmail.com>
On Sun, Jun 25, 2006 at 05:46:11PM +0200, FX Coudert wrote:
> >I'm curious if this should be selectable via something like
> >-minline-all-stringops resp. -f{no-}builtin-whatever?
> >
> >While it may give a nice performance boost, it most likely is something
> >e.g. -Os doesn't like, fwiw.
>
> You're right about -Os, though I don't think it needs an option all for
> itself. Also, we probably won't be inlining all string operations,
> because some would be a real pain to maintain if they were inside the
> front-end.
>
> What about simply call the library version if -Os is specified, i.e.
> make the new code conditional on optimize_size? Would that seem acceptable?
>
What are the sizes of aermod with and without your patch?
Checking Polyhedron's posted benchmark results suggest that
a 27% speed up is an important optizimation regardless of
the use of -Os.
--
Steve