This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] rtlopt branch merge part 5 -- loop unswitching
- From: law at redhat dot com
- To: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
- Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 31 Jan 2003 07:08:25 -0700
- Subject: Re: [PATCH] rtlopt branch merge part 5 -- loop unswitching
- Reply-to: law at redhat dot com
In message <20030131074948.GA27925@atrey.karlin.mff.cuni.cz>, Zdenek Dvorak wri
tes:
>Hello,
>
>> + /* Unswitch LOOPS. */
>>
>> I would expect to see at least a couple of paragraphs here saying what
>> "loop unswitching" does.
>
>use google? I really find little sense in explaining this; it would be
>other matter if it was something non-trivial, but this is something
>that simply cannot be done in much different way.
Unswitching is a pretty standard optimization concept that is found in
texts, papers, etc. You could put a reference to that material in
your code.
Alternately, you could make a little web page with a simple program
and show the before/after code after its loop as been unswitched.
>> There are *very few* comments at all in these
>> files and absolutely no overview of what they are doing.
>
>Sorry, but there are generally comments every 5-10 lines and I refuse
>to write more.
That's not a particularly good attitude.
Jeff