You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiling balar requires the user to comment out line 19 of balarTestCPU.cc. This line is #include <sst/core/simulation.h>, which does not exist. Replacing the line with #include <sst/core/simulation_impl.h> does not solve the compilation issue. Additionally, running the balar tests afterward produces a segmentation fault.
How to reproduce:
Compile balar by following the instructions at https://github.com/sstsimulator/sst-elements/blob/master/src/sst/elements/balar/README.md but comment out line 19 of balarTestCPU.cc so that compilation will complete. Next, run sst testBalar-testcpu.py --model-options='-c gpu-v100-mem.cfg -v -x vectorAdd/vectorAdd -t vectorAdd/cuda_calls.trace'. The test will complete and display the "Test Completed Successfully" message, then seg fault.
RHEL9 -- CUDA 11 -- SST core commit 0075ba17 -- SST elements commit 4c91414
The text was updated successfully, but these errors were encountered:
Compiling balar requires the user to comment out line 19 of
balarTestCPU.cc
. This line is#include <sst/core/simulation.h>
, which does not exist. Replacing the line with#include <sst/core/simulation_impl.h>
does not solve the compilation issue. Additionally, running the balar tests afterward produces a segmentation fault.How to reproduce:
Compile balar by following the instructions at https://github.com/sstsimulator/sst-elements/blob/master/src/sst/elements/balar/README.md but comment out line 19 of
balarTestCPU.cc
so that compilation will complete. Next, runsst testBalar-testcpu.py --model-options='-c gpu-v100-mem.cfg -v -x vectorAdd/vectorAdd -t vectorAdd/cuda_calls.trace'
. The test will complete and display the "Test Completed Successfully" message, then seg fault.RHEL9 -- CUDA 11 -- SST core commit 0075ba17 -- SST elements commit 4c91414
The text was updated successfully, but these errors were encountered: