an alias when the 'own_mem' parameter is fasle.
Several simplifications/tweaks related to Vector::NewMemoryAndSize
and Vector::MakeRef in BlockVector, GridFunction, LinearForm, and
ParBlockNonlinearForm.
Add more MFEM_ASSERTs in MemoryManager::Delete_.
Remove MemoryManager::RegisterAliasBases().
In Memory<T>::MakeAlias, register the 'base' when the globally
configured device memory type (which can be a host type, e.g. when
running on host) is a device memory type. Always registering the
'base' creates errors in the unit tests:
"alias already exists with different base/offset!"
which are probably due to dangling aliases. If we want to always
register the 'base', we need to address these errors.
Updated the unit test "MemoryManager/Scopes" to test for the new
behavior of Vector::NewMemoryAndSize.
Disable the unit test "MemoryManager" since it defined a Device
object which destroys the MemoryManager at the end of the test.
* The parameter of Vector::UseDevice(bool) no longer has a default value. All
the calls to UseDevice() in operator.cpp bilinearform_ext.cpp gridfunc.?pp and
linearform.?pp have been replaced with UseDevice(true).
* Added shortcuts for the device flags of the Memory objects inside the Vector
and Array classes:
bool Array::UseDevice()
bool Vector::UseDevice()
* The internal device flag in Memory::FlagMask is now called USE_DEVICE (it was
previously called EXEC_FLAG). The accessor function for this flag have been
renamed:
bool Memory::GetExecFlag() -> bool Memory::UseDevice()
void Memory::SetExecFlag(bool) -> void Memory::UseDevice(bool)
* Further renamed:
Memory::SyncWith -> Memory::Sync
Memory::SyncAliasToBase -> Memory::SyncAlias
Memory::SyncAliasToBase_ -> Memory::SyncAlias_
* Replaced FIXME with TODO in general/mem_manager.cpp
and transfers.
The Memory class is now used by some MFEM classes (like Array and
Vector) which can be used on the Device. Such classes now provide
methods to access the underlying Memory object, e.g. GetMemory.
Updated ex1/ex1p and ex6/ex6p to not need to enable/disable the
Device at specific points -- the Device is now enabled just at the
start. Also, the same examples can now run on Device (e.g. -d cuda)
without the partial assembly option (-pa) -- full assembly will
be still done on CPU but the sparse matrix action and vector
operations will be done using the Device.
Reverted changes in class DenseMatrix related to using the Device.
At this point, DenseMatrix operations are only used for small matrices
and using the Device in this case is not a good option.
Tzanio