Re: Beyond GCC 3.0: Summing Up

["Joseph S. Myers" <jsm28 at cam dot ac dot uk>]

On Wed, 11 Jul 2001, Stan Shebs wrote:

> how far afield GNU gets.  Several years ago, when I was maintaining
> GDB, the FSF forwarded me a bug report in paper mail that they'd

We removed the documented bug reporting address

GNU Compiler Bugs
Free Software Foundation
59 Temple Place - Suite 330
Boston, MA 02111-1307, USA

in GCC 3.0, though I don't know what was happening to those bugs for the
previous several years.

> The GDB process is a little more careful, since CVS can get corrupted
> and old data become irrecoverable, as people here have discovered,

The solution for this is for there to be proper regular backup procedures
(e.g. weekly full backups, which are archived permanently, and daily level
1 backups).  Though we could put weekly .tar.bz2 copies of the whole
repository on the FTP site and let the world mirror them.

In practice, a ,v file for a removed file that no-one is touching is far
less likely to be corrupted by bugs than ChangeLog,v which is touched by
every checkin to the parts of the compiler it covers.

> while releases are mirrored in many places around the world and
> are easily unpacked.  But in truth it probably doesn't matter a

Both GCC and GDB have old-releases directories which are widely mirrored
(and any target in question isn't going to have had any changes that
aren't purely consequential to changes elsewhere in the compiler made
since the last release).

-- 
Joseph S. Myers
jsm28@cam.ac.uk