From 2392877244da7bbcc2dba67abf506bfcf4908620 Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Wed, 3 Mar 2010 10:09:21 -0500 Subject: HACKING: emphasize embedded-c testing --- HACKING | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'HACKING') diff --git a/HACKING b/HACKING index 24986a9e..132794c8 100644 --- a/HACKING +++ b/HACKING @@ -96,11 +96,14 @@ the mailing list. Internal function, variable, probe identifiers should be prefixed with "_" for extra uniqueness, and not documented in the man pages. - 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. + 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. As they are a security hazard, every tapset + embedded-C routine should be pass-5 stress-tested for response to + erroneous inputs. This applies doubly to /* unprivileged */ ones. + 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. Embedded-C code that -- cgit