From: Paul Koning <pkoning@equallogic.com>
To: kenner@vlsi1.ultra.nyu.edu
Cc: gcc@gcc.gnu.org
Subject: Re: An issue for the SC: horrible documentation quality of GCC
Date: Fri, 09 May 2003 13:25:00 -0000 [thread overview]
Message-ID: <16059.44127.229367.375556@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <10305091217.AA14340@vlsi1.ultra.nyu.edu>
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
Richard> I want to repeat what I just said in a separate message: the
Richard> amount of totally undocumented code in GCC is approaching
Richard> very troublesome levels. There are who areas of the compler
Richard> in which nobody but their author can work due to a complete
Richard> lack of any high-level documentation....
Speaking as somone who has been trying to dig into gcc with the help
of gccint.*, I certainly agree. However...
Richard> (2) Remove any parts of the compiler for which documentation
Richard> is not supplied by the 3.4 release.
That doesn't seem very practical because you'd end up with much of the
compiler gone -- like the parser, and the code generator... :-(
FWIW, I think the situation with gcc is substantially better than,
say, gdb, or worse yet, binutils.
paul
next prev parent reply other threads:[~2003-05-09 13:25 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 12:12 Richard Kenner
2003-05-09 12:41 ` Michael Matz
2003-05-09 13:25 ` Paul Koning [this message]
2003-05-09 17:23 ` Joseph S. Myers
2003-05-09 20:30 ` Scott Robert Ladd
2003-05-09 14:01 Richard Kenner
2003-05-09 14:10 Richard Kenner
2003-05-09 14:37 ` Michael Matz
2003-05-09 15:36 Richard Kenner
2003-05-09 15:56 ` Daniel Jacobowitz
2003-05-09 15:57 ` Michael Matz
2003-05-09 16:34 ` David Edelsohn
2003-05-09 22:01 ` Jan Hubicka
2003-05-09 16:08 Richard Kenner
2003-05-09 21:04 ` Richard Henderson
2003-05-09 16:18 Richard Kenner
2003-05-09 22:06 ` Jan Hubicka
2003-05-09 16:39 Benjamin Kosnik
2003-05-09 18:22 ` Phil Edwards
2003-05-09 21:36 Richard Kenner
2003-05-09 22:19 ` Jan Hubicka
2003-05-09 22:17 Richard Kenner
2003-05-09 22:24 ` Jan Hubicka
2003-05-09 22:26 Richard Kenner
2003-05-09 22:44 ` Jan Hubicka
2003-05-09 22:48 ` Joe Buck
2003-05-10 12:07 ` Richard Earnshaw
2003-05-09 22:30 Richard Kenner
2003-05-09 22:51 ` Jan Hubicka
2003-05-09 22:51 Richard Kenner
2003-05-09 22:59 ` Jan Hubicka
2003-05-09 23:13 Richard Kenner
2003-05-09 23:23 ` Jan Hubicka
2003-05-10 2:21 Richard Kenner
2003-05-10 15:12 ` Zdenek Dvorak
2003-05-12 16:05 ` law
2003-05-12 16:20 ` Michael Matz
2003-05-12 17:39 ` law
2003-05-12 20:15 ` Richard Henderson
2003-05-10 15:29 Richard Kenner
2003-05-10 15:52 ` Zdenek Dvorak
2003-05-10 16:09 ` David Edelsohn
2003-05-10 16:17 ` Zdenek Dvorak
2003-05-10 16:57 ` Michael S. Zick
2003-05-12 9:07 ` Richard Earnshaw
2003-05-10 16:49 Richard Kenner
2003-05-11 19:42 ` Kai Henningsen
2003-05-10 17:04 Richard Kenner
2003-05-10 17:18 ` Zdenek Dvorak
2003-05-10 18:08 Richard Kenner
2003-05-11 19:58 Richard Kenner
2003-05-13 5:59 ` Michael S. Zick
2003-05-12 11:16 Richard Kenner
2003-05-12 11:36 Robert Dewar
2003-05-12 11:37 Robert Dewar
2003-05-12 16:25 Richard Kenner
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=16059.44127.229367.375556@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).