From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: rakdver@atrey.karlin.mff.cuni.cz
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] rtlopt branch merge part 5 -- loop unswitching
Date: Fri, 31 Jan 2003 14:52:00 -0000 [thread overview]
Message-ID: <10301311328.AA00953@vlsi1.ultra.nyu.edu> (raw)
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.
It still needs to be documented *in the source code*.
> 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.
The issue isn't the *frequency* of the comments but their size and content.
If you "refuse" to write more, than I strongly suggest we refuse to accept
your patches. GCC is a very large program and needs to be clearly and
carefully documented.
next reply other threads:[~2003-01-31 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 14:52 Richard Kenner [this message]
2003-01-31 15:10 ` Zdenek Dvorak
2003-01-31 15:00 Robert Dewar
2003-01-31 16:40 Richard Kenner
2003-01-31 16:41 ` Richard Earnshaw
2003-01-31 19:19 ` Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10301311328.AA00953@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).