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 14:13:08 EDT
- Subject: Re: An issue for the SC: horrible documentation quality of GCC
good luck. If you want them be really good, they must all work globally.
They must alst take into account what any other later optimization could
do. This is not feasible.
It isn't feasible to do it perfectly, of course not, but if we
properly specify what later optimizations do, it's not that unreasonable
to get something that makes the right decision the vast majority of the time.
Why it should not? You must gather the data on that you base your
decison, which definitely is not fast if you want to do it everywhere.
Usually that data is fairly cheap to get, such as a cost function.