From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Scott Bambrough <scottb@netwinder.org>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Regression testing...
Date: Tue, 18 Jan 2000 10:39:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.21.0001181935540.9133-100000@nunki.dbai.tuwien.ac.at> (raw)
In-Reply-To: <38848DA8.58C298FD@netwinder.org>
On Tue, 18 Jan 2000, Scott Bambrough wrote:
> I want to do some automated regression testing with the ARM ports of
> 2.95.1 and 2.95.2 before I put the RPM's up on netwinder.org. There
> used to be a web page on how to do it at sourceware, but I can't find
> it anymore. Is is still possible?
We had quite a bit of documentation, but removed it before the GCC 2.95
release which did not contain the testsuite due to legal reasons and
concerns by the FSF.
You still can access the old documentation at
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/wwwdocs/htdocs/install/test.html?rev=1.17&content-type=text/x-cvsweb-markup
I think we definitely should do something about making that public
again, else we *will* suffer a reduction in tests users do.
Unless I hear of any strong concerns against this, I plan to make
this page "active" again, with a note that/why the testsuite is not
included in releases.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
WARNING: multiple messages have this Message-ID
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Scott Bambrough <scottb@netwinder.org>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Regression testing...
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.21.0001181935540.9133-100000@nunki.dbai.tuwien.ac.at> (raw)
Message-ID: <20000401000000.B8e5kKmfdBDYAp5faeKXcnNHOnWMB5c-DqRY3GaxOE0@z> (raw)
In-Reply-To: <38848DA8.58C298FD@netwinder.org>
On Tue, 18 Jan 2000, Scott Bambrough wrote:
> I want to do some automated regression testing with the ARM ports of
> 2.95.1 and 2.95.2 before I put the RPM's up on netwinder.org. There
> used to be a web page on how to do it at sourceware, but I can't find
> it anymore. Is is still possible?
We had quite a bit of documentation, but removed it before the GCC 2.95
release which did not contain the testsuite due to legal reasons and
concerns by the FSF.
You still can access the old documentation at
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/wwwdocs/htdocs/install/test.html?rev=1.17&content-type=text/x-cvsweb-markup
I think we definitely should do something about making that public
again, else we *will* suffer a reduction in tests users do.
Unless I hear of any strong concerns against this, I plan to make
this page "active" again, with a note that/why the testsuite is not
included in releases.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2000-01-18 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-18 8:03 Scott Bambrough
2000-01-18 9:18 ` Richard Earnshaw
2000-04-01 0:00 ` Richard Earnshaw
2000-01-18 10:39 ` Gerald Pfeifer [this message]
2000-04-01 0:00 ` Gerald Pfeifer
2000-04-01 0:00 ` Scott Bambrough
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=Pine.GSO.4.21.0001181935540.9133-100000@nunki.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=scottb@netwinder.org \
/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).