| commit | 361fde346a1b8e058f53c19040754cc5cf2a3e65 | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Wed, 25 Feb 2015 13:40:34 +0000 (25 14:40 +0100) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Wed, 25 Feb 2015 13:40:34 +0000 (25 14:40 +0100) | ||
| tree | 6001b3ea953b09fcf4d6f29329109c32ad7758fc | treesnapshot (tar.gz zip) |
| parent | 556cf5b3c540c36d515a171db20f64c44b85ab41 | commitdiff |
remove clang from blacklist for openmp support
In ce4c754 (polybench_test.sh.in: do not perform openmp tests when using
clang, Thu Feb 5 13:10:48 2015 +0100) clang was blacklisted because
there were some issues with some PolyBench benchmarks. However, it turned
out that the problem was not caused by clang, but by a problem in
the initialization of the input for those benchmarks. In particular,
part of the array was not being initialized and while the contents
apparently defaulted to zero on most systems, this failed to be
the case when adding the -fopenmp flag on the clang command line.
Refrain from blacklisting clang.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
In ce4c754 (polybench_test.sh.in: do not perform openmp tests when using
clang, Thu Feb 5 13:10:48 2015 +0100) clang was blacklisted because
there were some issues with some PolyBench benchmarks. However, it turned
out that the problem was not caused by clang, but by a problem in
the initialization of the input for those benchmarks. In particular,
part of the array was not being initialized and while the contents
apparently defaulted to zero on most systems, this failed to be
the case when adding the -fopenmp flag on the clang command line.
Refrain from blacklisting clang.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
| m4/ax_check_openmp.m4 | diffblobblamehistory |