This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB 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: Technical criteria for retaining symbol readers

From: Andrew Cagney <cagney at gnu dot org>
To: Michael Elizabeth Chastain <mec dot gnu at mindspring dot com>
Cc: jimb at redhat dot com, gdb at sources dot redhat dot com
Date: Wed, 23 Jun 2004 16:14:12 -0400
Subject: Re: Technical criteria for retaining symbol readers
References: <20040623195109.E8A974B104@berman.michael-chastain.com>

jimb> I'd also like to have some kind of requirement for testability.

I would, too.  My preference would be that we look at gdb-testers@
and if there are no test results for feature X for the past N years,
that counts against keeping feature X.  gcc uses that as one factor
in deciding whether to obsolete stuff.

That's been suggested in the past. It was pointed out that some systems can't run the testsuite (DJGPP) so on its own it wasn't reasonable (neither is assuming that the presence of test results stops an architecture being removed :-).

Andrew

Follow-Ups:
- Re: Technical criteria for retaining symbol readers
  - From: Jim Blandy

References:
- Re: Technical criteria for retaining symbol readers
  - From: Michael Elizabeth Chastain

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