38 lines
2.0 KiB
Plaintext
Executable File
38 lines
2.0 KiB
Plaintext
Executable File
File: test3.c
|
|
Original provenience: Universitaet des Saarlandes, Saarbruecken, Germany
|
|
Compiler Research Group
|
|
|
|
2015-10-18:
|
|
- Removed original header comment, replaced by TACLeBench header.
|
|
- Added prefix "test3_" to all global symbols.
|
|
- Added explicit forward declarations of functions.
|
|
- Replaced initialization code by TACLeBench-compliant initialization code.
|
|
Added pseudo-random initialization of the global arrays "test3_array1" ...
|
|
"test3_array8".
|
|
- Added new function test3_return producing a checksum as return value.
|
|
- Added new function test3_main according to TACLeBench guidelines.
|
|
test3_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
|
|
- Sanity check: Replaced all expressions 'x >> 1' by 'x >>= 1' in order to
|
|
eliminate compiler warnings showing that 'x >> 1' makes no sense.
|