On Fri, Apr 12, 2002 at 01:17:51PM -0700, Gareth Hughes wrote:
|
| Perhaps we need a "-pedantic"-like command-line option to force more
| stringent tests?
We'd still have to figure out how stringent the test should be, and in a
lot of cases that's unclear to me. (e.g. texture accuracy involves the
color depth of the framebuffer, the color depth of the texture, the
filtering algorithm used, and the width of the filtering datapath, not
all of which can be queried by the test.)
Another approach might be to add an option that means "forget pass/fail,
just give me the raw accuracy measurements." Or perhaps add tests that
produce subjective quality assessments ("NOTE: Texturing accuracy is
always as good as the minimum of the framebuffer and texture color
depths").
Part of the uncertainty is due to not knowing the audience for the
tests. Driver developers have needs that differ from those of
application developers. I suppose we could use test lists to select
just the results that are of interest to each audience.
Allen
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
