This is the mail archive of the
mailing list for the GCC project.
Re: Loop unroll fixes
- To: Joe Buck <jbuck at synopsys dot COM>
- Subject: Re: Loop unroll fixes
- From: law at redhat dot com
- Date: Mon, 24 Sep 2001 10:33:27 -0600
- cc: jsm28 at cam dot ac dot uk (Joseph S. Myers), mrs at windriver dot com (mike stump), rth at redhat dot com, dewar at gnat dot com, gcc at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <200109191827.LAA19330@atrus.synopsys.com>you write:
> Joseph Myers writes:
> > A harder case might be where the bug was shown up by a small testcase fro
> > a proprietary testsuite (see e.g.
> > <URL:http://gcc.gnu.org/ml/gcc-patches/1998-11/msg00257.html>). Do we
> > have any legal guidance on what is and is not safe to do in such cases?
> We got some legal advice from Eben Moglen (FSF counsel) on test suite
> issues. We could perhaps ask him for advice on how to legally create a
> test case that we can distribute. But the following procedure is
> generally considered safe:
> programmer A, with access to the test case, writes up a report on what
> the test is doing and what the failure is.
> (for the extremely paranoid: lawyer reads report, sprinkles holy water,
> but probably unneeded in this case)
> programmer B uses the report to write a test case that shows the same
Right. In fact, this kind of discipline (IMHO) would generally lead to
more thorough bug analysis and hopefully fewer incorrect patches.