Go to the source code of this file.
|
| None | peano4.api.taskgraph.compiler.DeriveLoadStoreComputeFlag.derive_load_store_compute_flag (List["peano4.api.solversteps.Step"] steps) |
| | For every submodel used anywhere in steps, derive a peano4::grid::constructLoadStoreComputeFlag(...) expression from which of its using Steps are active, and assign it to that submodel's generator.load_store_compute_flag - the runtime counterpart to peano4.api.taskgraph.compiler.PropagateUseStatements.propagate_use_statements(), which has to run before whichever compiler produces these steps: it decides which tasks have to declare a submodel at all; this function decides, for every Step that does, what its generated Observer should actually do with the data once the submodel's stack storage puts it there (load a real value, or start from a fresh dummy; store the result back, or discard it) - by asking, at runtime, which Step is presently executing.
|
| |
| str | peano4.api.taskgraph.compiler.DeriveLoadStoreComputeFlag._step_active_expression ("peano4.api.solversteps.Step" step) |
| |
| | peano4.api.taskgraph.compiler.DeriveLoadStoreComputeFlag._load_store_compute_flag_holder (submodel) |
| | The object holding the submodel's load_store_compute_flag: The peano4_mpi_and_storage_aspect for DaStGen2 data, the generator otherwise.
|
| |
| None | peano4.api.taskgraph.compiler.DeriveLoadStoreComputeFlag._ensure_step_repository_includes (holder) |
| |
| None | peano4.api.taskgraph.compiler.DeriveLoadStoreComputeFlag._derive_load_store_compute_flag_for_one_kind (List["peano4.api.solversteps.Step"] steps, str attribute_name, str access_attribute_name, str guard_routine_name) |
| |