testing refactor

CHANGELOG.md

@@ -1,6 +1,15 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
+## [Unreleased]
+
+### Removed
+- Remove support for ComputeCpp compiler
+
+### Changed
+- Removed std-data/std-indices memory management workaround for AdaptiveCpp
+
+
 ## [v5.0] - 2023-10-12
 ### Added
 - Ability to build Kokkos and RAJA versions against existing packages.

CMakeLists.txt

@@ -31,8 +31,8 @@ endmacro()
 # the final executable name
 set(EXE_NAME babelstream)
 
-# for chrono and some basic CXX features, models can overwrite this if required
-set(CMAKE_CXX_STANDARD 11)
+# for chrono, make_unique, and some basic CXX features, models can overwrite this if required
+set(CMAKE_CXX_STANDARD 14)
 
 if (NOT CMAKE_BUILD_TYPE)
     message("No CMAKE_BUILD_TYPE specified, defaulting to 'Release'")

LICENSE

@@ -14,9 +14,7 @@
 *     with the following limitations:
 *     3a. In order to be referred to as "BabelStream benchmark results",
 *         published results must be in conformance to the BabelStream
-*         Run Rules published at
-*         http://github.com/UoB-HPC/BabelStream/wiki/Run-Rules
-*         and incorporated herein by reference.
+*         Run Rules incorporated herein by reference.
 *         The copyright holders retain the
 *         right to determine conformity with the Run Rules.
 *     3b. Results based on modified source code or on runs not in
@@ -33,3 +31,20 @@
 *     program constitutes acceptance of these licensing restrictions.
 *  5. Absolutely no warranty is expressed or implied.
 *———————————————————————————————————-------------------------------------------
+* Run Rules:
+*
+* In order to generate a valid BabelStream result measuring
+* *main memory bandwidth*, you should obey the following rules:
+*
+* 1. The array size must be large enough that increasing the array size does not
+* drastically change the reported bandwidth. If you satisfy this you will no
+* longer be affected by any cache effects.
+*
+* 2. Each kernel should take a few milliseconds. The resolution of the host timer
+* is probably in milliseconds so each kernel execution should be longer than the
+* timer resolution. Increase the array size if the kernels are too fast. You are
+* unlikely to break this rule if you follow rule 1.
+*
+* If you see a single BabelStream result, expect this to be the largest bandwidth
+* reported by the benchmark unless stated otherwise.
+*———————————————————————————————————-------------------------------------------