Add wasm tacle-bench targets

targets/wasm-tacle/kernel/bitonic/ChangeLog.txt

@@ -0,0 +1,53 @@
+File: bitonic.c
+Original provenience: StreamIt benchmark suite,
+	 	      http://groups.csail.mit.edu/cag/streamit/results/bitonic/code/c/
+
+2015-10-20:
+- Removed original header comment, replaced by TACLeBench header.
+- Added prefix "bitonic_"/"BITONIC_" to all global symbols
+- adjusted names of bitonicSort and bitonicMerge functions to
+  bitonic_*.
+- Replaced initialization code by TACLeBench-compliant initialization code.
+- Added new function quicksort_return producing a checksum as return value.
+- Added new function quicksort_main according to TACLeBench guidelines.
+  quicksort_main is annotated as entry-point for timing analysis.
+- 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
+  - Names of functions and global variables all start with a benchmark-specific
+    prefix (here: bs_) followed by lowercase letter (e.g., bs_square)
+  - 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
+
+
+2016-02-01:
+- More formatting:
+  - In non-empty lists or index expressions, opening '(' and '[' are followed by
+    one whitespace, closing ')' and ']' are preceded by one whitespace
+  - Operators within expressions shall be preceded and followed by one
+    whitespace
+
+
+2016-04-05:
+- Return '0' on success
+
+2016-04-06:
+- Fixed generation of return value
+
+2016-06-01:
+- Changed all prefixes to lower-case
+