This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documentation: Bugs
- To: Jonas Rathert <jrt at gmx dot de>
- Subject: Re: Documentation: Bugs
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Wed, 28 Jul 1999 22:11:12 +0200 (MET DST)
- cc: gcc at gcc dot gnu dot org
On Wed, 28 Jul 1999, Jonas Rathert wrote:
> while going through the web-pages I found the buglist: bugs.html.
> [...]
> Anyway, this file should be updated before the release of gcc-2.95!
That would be nice, but, as Jeff noted, it is not critical.
> I'd suggest to create a subdirectory bugs/ which contains files
> egcs-1.1.html, egcs-1.2.html and gcc-2.95.html.
If we go that road, we should re-use the current directory structure
with egcs-1.0, egcs-1.1 and gcc-2.95.
> This way we can "freeze" the known bugs of egcs* (for users coming
> late or using e.g. Linux distributions with older egcs-compilers) and
> start a new buglist for gcc-2.95 (which will propably grow after the
> release of gcc-2.95).
I think we should not care too much about old versions of GCC, where
currently old means GCC 2.8.x and EGCS 1.0.x and I am not sure how
maintainable separate bug lists will be.
If we have volunteers willing to maintain such pages and keep them
up-to-date that might change my opinion, but as you noticed, even
keeping the current single page up-to-date is not easy.
> Another way is to create one big file with different sections for
> different compiler versions.
How about having a list with frequently encountered bugs in the current
(GCC 2.95.x) and previous (EGCS 1.1.x) releases together with detailed
information which release suffers from which bug and information when
resp. whether a bug has been fixed?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/