From a9a29deb6ee0f9e38dea288e12477acb5f672f32 Mon Sep 17 00:00:00 2001 From: fche Date: Mon, 9 Jan 2006 18:14:58 +0000 Subject: 2006-01-09 Frank Ch. Eigler * HACKING: Extend guidelines for tapset testing. --- ChangeLog | 4 ++++ HACKING | 13 ++++++++----- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index 0c857bba..ebfa15c6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2006-01-09 Frank Ch. Eigler + + * HACKING: Extend guidelines for tapset testing. + 2006-01-06 Will Cohen * Makefile.am (gcov,lcov): Don't remove .gcno .gcda files. diff --git a/HACKING b/HACKING index 2be2fc0f..09acecf6 100644 --- a/HACKING +++ b/HACKING @@ -72,11 +72,14 @@ the mailing list. identifiers should be prefixed with "_" for extra uniqueness, and not documented in the man pages. - New or changed embedded-C code should be accompanied by a test case - in the /src/testsuite/buildok/ bucket to assert its buildability, - and ideally pass-5 tests to assert correct behavour. Embedded-C - code should avoid making references to the runtime or other code - possibly generated by the translator. + Tapsets should come with a tests cases that provide good test coverage. + Every alias definition should be tested for pass-2 correctness. Every + embedded-C routine should be tested for pass-4 buildability and ideally + pass-5 correctness. The platforms/architectures against which the tapset + was tested should be published, and ideally asserted by code. + + Embedded-C code should avoid making references to the runtime or + other code possibly generated by the translator. - runtime -- cgit