This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC testsuite maintenance (was: [PATCH] Fix OpenACC vector_length parsing in fortran)

From: Joseph Myers <joseph at codesourcery dot com>
To: Thomas Schwinge <thomas at codesourcery dot com>
Cc: Jakub Jelinek <jakub at redhat dot com>, <gcc at gcc dot gnu dot org>, Cesar Philippidis <cesar at codesourcery dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Fortran List <fortran at gcc dot gnu dot org>
Date: Mon, 25 Jul 2016 16:37:07 +0000
Subject: Re: GCC testsuite maintenance (was: [PATCH] Fix OpenACC vector_length parsing in fortran)
Authentication-results: sourceware.org; auth=none
References: <57884500.9040906@codesourcery.com> <871t2ve46e.fsf@kepler.schwinge.homeip.net> <20160715082113.GR7387@tucnak.redhat.com> <87a8hjmenq.fsf@hertz.schwinge.homeip.net>

On Fri, 15 Jul 2016, Thomas Schwinge wrote:

> > No, we want to have as little churn as possible in existing tests, the
> > general policy is to add new tests (not just for OpenACC/OpenMP, but for
> > all functionality).
> 
> Hmm, that's something I had not been aware of, and I can't find this
> covered in the documentation.  So, you're basically saying that files in
> the testsuite are write-once, and should not be maintained aside from
> fixing errors, adjusting due to optimization changes, or due to changed
> diagnostics, and the like?  (Of course, I do agree that we shouldn't

Yes, that's my view.  It makes it easier to distinguish regressions from 
new tests that fail (on some platforms) if what a test tests doesn't 
change unnecessarily.

-- 
Joseph S. Myers
joseph@codesourcery.com

Follow-Ups:
- Re: GCC testsuite maintenance (was: [PATCH] Fix OpenACC vector_length parsing in fortran)
  - From: Mike Stump

References:
- [PATCH] Fix OpenACC vector_length parsing in fortran
  - From: Cesar Philippidis
- Re: [PATCH] Fix OpenACC vector_length parsing in fortran
  - From: Thomas Schwinge
- Re: [PATCH] Fix OpenACC vector_length parsing in fortran
  - From: Jakub Jelinek
- GCC testsuite maintenance (was: [PATCH] Fix OpenACC vector_length parsing in fortran)
  - From: Thomas Schwinge

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]