compilation warning with g++15

[mattijsjanssens]

Describe the bug

Small one : compilation warning:

In file included from /Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/event/event_store_recorder.hpp:12,
                 from /Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/event/recorder_factory.hpp:10,
                 from /Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/event/event.hpp:21,
                 from /Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/Allocator.inl:12,
                 from /Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/Allocator.hpp:243,
                 from memory/MemoryPool.cxx:42:
/Volumes/case_sensitive/OpenFOAM/work/ThirdParty-common/platforms/darwin64Gcc15/umpire-2025.03.0/include/umpire/event/event_store.hpp:23:7: warning: 'class umpire::event::event_store' has virtual functions and accessible non-virtual destructor [-Wnon-virtual-dtor]
   23 | class event_store {

Compilers & Libraries (please complete the following information):

• Compiler & version: [e.g. GCC 4.9.3]: g++15
• CUDA version (if applicable):

[kab163]

Are you using Umpire v2025.03.0? If so, that would be why you're seeing that. It looks like the virtual destructor was added in the next release of Umpire (v2025.12.0). So if you bump your Umpire version up to the latest, the warning should be gone.

I built with Umpire@develop with gcc15 and did not see that warning.