Add wasm tacle-bench targets

targets/wasm-tacle/test/cover/ChangeLog.txt

@@ -0,0 +1,57 @@
+File: cover.c
+Original provenience: Mälardalen benchmark suite,
+Source: http://www.mrtc.mdh.se/projects/wcet/wcet_bench/cover/cover.c
+
+2016-03-15:
+- Made sure that cover_return returns value 0.
+
+2016-01-06:
+- Added original name to generic TACLeBench header.
+- Applied TACLeBench formatting rules via
+  astyle --options=doc/example/astylerc.txt
+
+2015-12-03:
+- Replaced comment describing purpose of benchmark from lines 1-7
+  with generic TACLeBench header.
+- Removed all "/* k switch case traversed */ comments.
+  (lines 10, 144, 218)
+- Introduced comments to split file in sections for forward declarations,
+  global variables, initialization-related and return-value-related functions,
+  core benchmark functions, and main routine.
+- Renamed function swi10 to cover_swi10.
+- Renamed function swi50 to cover_swi50.
+- Renamed function swi120 to cover_swi120.
+- Renamed function main to cover_main.
+- Replaced local variable cnt in cover_main with global variable cover_cnt.
+- Added function cover_init that handles the initialization of cover_cnt.
+- Added function cover_return that handles the original return value of main.
+- Changed cover_main such that no value is returned.
+- Added new function main that first calls cover_init, then cover_main and
+  finally returns the return value of cover_return.
+- Added forward declarations for all these functions.
+- Applied code formatting according to the following rules:
+  - Lines shall not be wider than 80 characters; whenever possible, appropriate
+    line breaks shall be inserted to keep lines below 80 characters
+  - Indentation is done using whitespaces only, no tabs. Code is indented by
+    two whitespaces
+  - Two empty lines are put between any two functions
+  - In non-empty lists or index expressions, opening '(' and '[' are followed by
+    one whitespace, closing ')' and ']' are preceded by one whitespace
+  - In comma- or colon-separated argument lists, one whitespace is put after
+    each comma/colon
+  - For pointer types, one whitespace is put before the '*'
+  - Operators within expressions shall be preceded and followed by one
+    whitespace
+  - Code of then- and else-parts of if-then-else statements shall be put in
+    separate lines, not in the same lines as the if-condition or the keyword
+    "else"
+  - Opening braces '{' denoting the beginning of code for some if-else or loop
+    body shall be put at the end of the same line where the keywords "if",
+    "else", "for", "while" etc. occur
+  - Function arguments are specified in ANSI style, i.e.,
+      float my_sqrtf( float val )
+    and NOT in Kernighan&Ritchie style like, e.g.,
+      float my_sqrtf( val )
+        float val;
+- Tested conformance to C90 via
+  clang -fsyntax-only -Weverything -Wno-unknown-pragmas -pedantic -std=c90