public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "Timothy D. Witham" <wookie@osdl.org>
Cc: Luigi Genoni <kernel@Expansa.sns.it>,
	Mike Galbraith <mikeg@wen-online.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stp@osdl.org
Subject: Re: Regression testing of 2.4.x before release?
Date: Mon, 12 Nov 2001 20:53:28 -0800	[thread overview]
Message-ID: <3BF0A748.A68251C6@kegel.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111041955290.30596-100000@Expansa.sns.it>  <3BE5F0B5.52274D07@kegel.com> <1004978377.1226.22.camel@wookie-laptop.pdx.osdl.net>  <3BEF6B1B.1E077ED9@kegel.com> <1005592054.16715.35.camel@wookie-laptop.pdx.osdl.net>

"Timothy D. Witham" wrote:
> 
> On Sun, 2001-11-11 at 22:24, Dan Kegel wrote:
> > At some point it might be nice to also use the STP to help
> > speed gcc 3 development, too.  (I personally am really
> > looking forward to the day when I can use the same compiler
> > for both c++ and kernel.)
> 
>   Strange, I was just talking to somebody about compiler
> performance and regression issues and what sort of automation
> could be done to do that sort of testing.
> 
>   Since the STP is really a framework and just about any piece
> of software and testing environment could be worked into it.
> 
>  So I guess you could have two pieces.  One that just ran a bunch
> of compile and user level tests and then one that went in and
> checked out the compiler on a kernel tree and then ran the
> same performance tests that had been run using the "standard"
> compiler.

Go/no-go tests, where you make sure a kernel compiled with gcc 3
actually works, might be appropriate for starters.  I don't know
if that's been established yet.

>   Are you stepping forward to integrate this into STP? :-)

I wish!  Alas, tendinitis makes hacking hazardous for me for now.

- Dan

  reply	other threads:[~2001-11-13  4:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0111040832060.364-100000@mikeg.weiden.de>
2001-11-04 17:58 ` Regression testing of 2.4.x before release? Dan Kegel
2001-11-04 19:09   ` Luigi Genoni
2001-11-05  1:51     ` Dan Kegel
2001-11-05 16:39       ` Timothy D. Witham
2001-11-12  6:24         ` Dan Kegel
2001-11-12 19:07           ` Timothy D. Witham
2001-11-13  4:53             ` Dan Kegel [this message]
2001-11-13 22:00               ` STP for automated GCC testing (was Re: Regression testing of 2.4.x beforerelease?) Bryce Harrington
2002-01-10 23:50           ` Regression testing of 2.4.x before release? Daniel Phillips
2002-01-10 23:50           ` Daniel Phillips
2002-01-12  0:04             ` M. Edward (Ed) Borasky
2002-01-12  0:29               ` eddantes
2002-01-12  0:34               ` [OT] " Kurt Garloff
2001-11-04  7:03 Dan Kegel
2001-11-04  7:15 ` Ted Deppner
2001-11-04 12:04   ` Tahar
2001-11-04 17:27     ` Ted Deppner
2001-11-04 18:41     ` Luigi Genoni

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=3BF0A748.A68251C6@kegel.com \
    --to=dank@kegel.com \
    --cc=kernel@Expansa.sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=stp@osdl.org \
    --cc=wookie@osdl.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