[M3devel] portable/less portable test variations

Jay K jay.krell at cornell.edu
Sun Feb 28 10:54:44 CET 2010


I commited something here.

 

 

The function in m3tests/m3makefile is "mixed_portability_test".

p227 uses it.

 

 

The test can be run with no parameters, in which case the output is "fully portable" (the

same on all targets) and the output is compared with the "unadorned" stdout.pgm, etc.

 

And it can be run with the flag -include-less-portable-output, in which case we probe

for, e.g.:

 

 stdout.pgm32

 stdout.pgm-little_endian32

 stdout.pgm-little_endian

 

(or "64" or "big")

 

 

The automated tests will run both variations.

 

 

As well, the preexisting recent default was to probe, as we had a few

cases that needed "stdout.pgm64". We should clean this up so those

are called out specifically.

 

 

This way, e.g. PPC can be compared to SPARC, I386_* can

be compared amongst each other, with more coverage than

might be had if just all platforms compared against all platforms

and the coverage constrained.

 

 

 - Jay

 


From: jay.krell at cornell.edu
To: m3devel at elegosoft.com
Subject: portable/less portable test variations
Date: Wed, 24 Feb 2010 12:41:12 +0000



I'd like to write tests that, given different command line parameters,
will either output totally portable results, or only somewhat portable, where "somewhat"
probably means either portable to particular wordsize or portable to wordsize+endian.
Worst case, completely platform specific.
 
We'd have 1, 3, or 5 checked in expected results.
  Or possibly 1+n (portable + n platforms).
  This case is less useful, because it takes away the ability to compare, e.g. LINUXLIBC6 to NT386.
 
The test would run twice, with and without the command line option.
 
I guess it is about as much work to implement as to describe, but I've let it drag out.
 
I have tests that would benefit from this.
 
 - Jay

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100228/4073fa41/attachment-0002.html>


More information about the M3devel mailing list