This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: g++ memory bug.
- To: Theodore dot Papadopoulo at sophia dot inria dot fr, mark at markmitchell dot com
- Subject: Re: g++ memory bug.
- From: mrs at wrs dot com (Mike Stump)
- Date: Fri, 8 Jan 1999 07:43:20 -0800
- Cc: Jose dot Gomes at sophia dot inria dot fr, egcs-bugs at cygnus dot com, egcs-patches at cygnus dot com
> Date: Fri, 08 Jan 1999 14:42:48 +0100
> From: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>
> On the other hand, it seems to me that in this specific case the
> variables are not used and will be removed by the optimizer
Nope, not removed yet (if you refer to the members). In general, only
through link time feedback can we do this type of transformation, as
another file or library may in fact do something with them. If you
mean the one in main, then yes, it should wind up going.
> I checked what does KaiC++ and it looks like there is only one level
> of inlining which explains very well why the program compiles but
> execution times are increase exponentially with the level of
> recursive templates.
> In this regard, egcs does much better since when it is able to do the
> full inlining as it suppresses all the calls....
It is nice to see that we do better than Kai...