This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: An issue for the SC: horrible documentation quality of GCC
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rakdver at atrey dot karlin dot mff dot cuni dot cz
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 10 May 03 13:09:08 EDT
- Subject: Re: An issue for the SC: horrible documentation quality of GCC
I guess that for every such heuristic you will with some care find an
example where it does a stupidity. In general it makes more sense to
have a few passes with really good heuristics than have some lame
heuristic in every pass.
No, all should be good! The strength of GCC is that it does optimization
everywhere. We should not sacrifice that.
As for the speed -- I guess this is just a matter of opinion, as there
is nothing to compare. My opinion is that the increased speed of most
of the passes would pay up for the decreased speed of a few cleanup
passes (they must be in some form present anyway, they already must
gather all the data, so the slowdown should not be that dramatic).
Increased over what? Why does a heuristic slow things down?