Ignacio Laguna

FT: return error codes are not saved or handled (mostly romio)

16

I would like to report some issues on how return error codes are propagated and handled in the library. We are developing a static analysis framework that detects the code...

Function pointers should not be instrumented

1

This was incorrectly instrumented: This line: `fptr[idx_dst] = (*fine_volumes)(SAMRAI::pdat::CellIndex(*bi));` Became: `fptr[idx_dst] = _FPC_CHECK_((*fine_volumes)(SAMRAI::pdat::CellIndex(* bi), ), 125, “..ineOperator.cxx”);` Here a function pointer is assigned to an array element.

Add support for checking on basic operations(+,-,*,/): from this: `_FPC_CHECK(x + y - z)` change to this: `_FPC_CHECK(x + _FPC_CHECK(y - _FPC_CHECK(z)))`

Currently tests assume a fixed compute capability of sm_65. We should provide a mechanism to determine the compute capability dynamically (when tests are run).

We need to provide a platform-independent RAJA test for the llvm version

Test from master run on python 2.x and tests for clang_plugin runs on python 3.x. We should be consistent.

We should add functionality to check for almost subnormal numbers in the host checks.

The plugin tests are not functional when we make the tool.

In the Runtime.h file the following declaration causes problems: `__device__ static char *_FPC_FILE_NAME_[1];` When optimizations are applied, this global variable is lost (or optimized out), but we need to find...

Functions declarations have HOST_DEVICE_CUDA but definitions

2

In MC_Particle.hh: Function declaration of Move_Particle uses HOST_DEVICE_CUDA: ``` HOST_DEVICE_CUDA void Move_Particle(const DirectionCosine & direction_cosine, const double distance); ``` but function definition does not: `inline void MC_Particle::Move_Particle( const DirectionCosine &my_direction_cosine,...