From: Joe Buck <jbuck@synopsys.COM>
To: jsm28@cam.ac.uk (Joseph S. Myers)
Cc: mrs@windriver.com (mike stump),
rth@redhat.com, dewar@gnat.com, gcc@gcc.gnu.org
Subject: Re: Loop unroll fixes
Date: Wed, 19 Sep 2001 11:28:00 -0000 [thread overview]
Message-ID: <200109191827.LAA19330@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109182015080.1098-100000@kern.srcf.societies.cam.ac.uk>
Joseph Myers writes:
> A harder case might be where the bug was shown up by a small testcase from
> 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
failure.
next prev parent reply other threads:[~2001-09-19 11:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 11:54 mike stump
2001-09-18 12:34 ` Joseph S. Myers
2001-09-19 11:28 ` Joe Buck [this message]
2001-09-24 9:31 ` law
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 1:12 Wolfgang Bangerth
2001-10-10 1:16 ` Mark Mitchell
2001-10-10 5:14 ` Franz Sirl
2001-10-10 11:08 ` Mark Mitchell
2001-09-18 17:36 Richard Kenner
2001-09-18 10:47 Benjamin Kosnik
2001-09-18 4:16 Richard Kenner
[not found] <200109142021.QAA26236@makai.watson.ibm.com>
2001-09-15 8:57 ` Bernd Schmidt
2001-09-17 13:16 ` Richard Henderson
2001-09-17 14:24 ` Joe Buck
2001-09-17 15:11 ` Richard Henderson
2001-09-17 17:22 ` Mark Mitchell
2001-09-18 2:19 ` Joseph S. Myers
[not found] <Pine.LNX.4.33.0109141957550.29416-100000@host140.cambridge.redhat.com>
2001-09-14 14:36 ` David Edelsohn
2001-09-13 16:35 Zoltan Hidvegi
2001-09-13 18:58 ` David Edelsohn
2001-09-13 23:50 ` Jim Wilson
2001-09-14 6:55 ` Daniel Berlin
2001-09-14 12:15 ` Joseph S. Myers
2001-09-14 16:45 ` Jim Wilson
2001-09-14 20:11 ` David Edelsohn
2001-09-14 22:23 ` Jim Wilson
2001-09-15 2:42 ` Bernd Schmidt
2001-09-14 21:16 ` Daniel Berlin
2001-09-14 9:41 ` David Edelsohn
2001-09-14 10:46 ` Bernd Schmidt
2001-09-14 11:47 ` David Edelsohn
2001-09-14 17:54 ` Jim Wilson
2001-09-14 18:35 ` David Edelsohn
2001-09-14 19:56 ` Jim Wilson
2001-09-15 2:56 ` Joseph S. Myers
2001-10-04 6:46 ` Franz Sirl
2001-10-04 7:40 ` Mark Mitchell
2001-10-04 20:46 ` Jim Wilson
2001-10-04 20:51 ` Mark Mitchell
2001-10-04 23:10 ` Zoltan Hidvegi
2001-10-10 0:05 ` Mark Mitchell
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=200109191827.LAA19330@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=mrs@windriver.com \
--cc=rth@redhat.com \
/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).