search

LLNL / ExaConstit

A crystal plasticity FEM code that runs on the GPU
BSD 3-Clause "New" or "Revised" License
47 stars 13 forks source link

Potential bug when using MFEM and ExaConstit debug builds at same time #5

Closed rcarson3 closed 4 years ago

rcarson3 commented 4 years ago

I ran into issues where if I had rcarson/mfem/exaconstit-dev fork being used with conjunction with a ExaConstit/mfem_forall_dev branch that the build was barfing when trying to compile the 1st file. If I didn't have ExaConstit configured to being built in debug mode it worked fine.

I need to run this issue down and see if it's a problem with my linux desktop build or if it's happening on other platforms as well. I've never had this happen before in the past when making use of debug builds with both systems at least on a LC machines...

rcarson3 commented 4 years ago

It's the inclusion of this flag -DDEBUG that's causing the issue.

I'm getting a long list of errors bu the first set is:

<command-line>:0:7: error: expected identifier before numeric constant
<command-line>:0:7: error: expected '}' before numeric constant
<command-line>:0:7: error: expected unqualified-id before numeric constant
In file included from /mfem/install_dir/include/mfem/mfem.hpp:18:0,
                 from /mfem/install_dir/include/mfem.hpp:2,
                 from /ExaConstit/src/BCData.cpp:2:
/mfem/install_dir/include/mfem/general/device.hpp:79:18: error: 'CPU' was not declared in this scope
       CPU_MASK = CPU | RAJA_CPU | OCCA_CPU | CEED_CPU,
rcarson3 commented 4 years ago

The scripts/meshing/CMakelist.txt introduced this flag which we don't really need. I'll remove it so bugs no longer crop up on the MFEM side of things.