compiler: Add machinery for custom memory allocators and MPI #1764
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1764 +/- ##
===========================================
- Coverage 89.52% 62.43% -27.09%
===========================================
Files 209 209
Lines 33879 33927 +48
Branches 4404 4406 +2
===========================================
- Hits 30330 21183 -9147
- Misses 3050 12133 +9083
- Partials 499 611 +112
Continue to review full report at Codecov.
|
FabioLuporini
force-pushed
the
generalize-mpi-modes
branch
3 times, most recently
from
bd16d58
to
787bf1f
Compare
|
|
||
| * ALLOC_GUARD: Only used in so-called "develop mode", to trigger SIGSEGV as |
There was a problem hiding this comment.
develop-mode or develop_mode just for 'grepping' homogeneity
Basically no because I'm not adding any new functionalities |
FabioLuporini
force-pushed
the
generalize-mpi-modes
branch
from
787bf1f
to
e116845
Compare
not really... we could create a mapping for one of the existing ones... but what for? |
|
as in, just to clarify. All the code added by this PR is already tested automatically by the current tests, as the execution flow goes through all the touched classes and functions. That's why I wrote above that we're basically good to go |
| @@ -590,13 +590,13 @@ def _bounds_glb_to_loc(cls, dec, m, M): | |||
|
|
|||
| def __subdomain_finalize__(self, dimensions, shape, distributor=None, **kwargs): | |||
| """ | |||
| Must be overridded by subclasses. | |||
| Must be overridden by subclasses. | |||
There was a problem hiding this comment.
@georgebisbas as promised, fixed it here
No description provided.