YAXT: Issueshttps://swprojects.dkrz.de/redmine/https://swprojects.dkrz.de/redmine/redmine/favicon.ico?17095821032015-04-23T09:45:59ZDKRZ projects
Redmine Bug #335 (New): passing pointers of zero-size arrays to redistshttps://swprojects.dkrz.de/redmine/issues/3352015-04-23T09:45:59ZMoritz Hanke
<p>The addresses of arrays passed to xt_redist_s_exchange can be NULL, when the size of the array is zero. This can cause problems especially when redist collections are used.<br />For zero-sized arrays a redist should not contain any message. When this happens we might have to consider applying some kind of special handling.<br />When the Fortran interface is used, no appropriate C_LOC-pointer can be generated.</p>
Tasks:
<ul>
<li>reproduce problem with test (only occurs with certain MPIs)</li>
<li>fix problem of define that NULL pointers are not allowed</li>
</ul> Bug #331 (New): Make xt_xmap_distdir work when less data than expected gets packedhttps://swprojects.dkrz.de/redmine/issues/3312014-07-31T08:37:03ZThomas Jahnsjahns@dkrz.de
<p>commit:daacfe17cb9124f4f0f3763858cc94ff666efb4a fixes a problem in xmap_all2all that is also present in the distributed directory variant: if the get_pack_size method of an index list returns a value that is larger than the actual advance of position that happens due to the pack method, distdir fails.</p>
<p>Steps to reproduce: simply add one to the MPI_Packsize count argument of e.g. source:src/xt_idxvec.c#L369</p> Bug #318 (Closed): Eliminate multi-source indiceshttps://swprojects.dkrz.de/redmine/issues/3182013-03-11T15:26:34Zredmine administratorredmine@dkrz.de
<p>In case one index has multiple providers, it is currently also written multiple times to each destination. This needs to be changed such that each index is only written to once.</p>
<p>This should be implemented within xt_xmap_intersection_new to retain the functionality for all derived xmap constructors.</p> Bug #313 (Closed): bug: xmap construction allows multiple writes to the same destination memory l...https://swprojects.dkrz.de/redmine/issues/3132013-01-17T10:12:09ZJoerg Behrensbehrens@dkrz.de
<p>If multiple source processes have the same index that is required by a target then all of these source processes may be registered as data sources which may lead to collisions when the actual data exchange happens. Also, this may lead to a bloated xmap.</p> Bug #302 (Closed): Naminghttps://swprojects.dkrz.de/redmine/issues/3022012-04-23T12:36:25ZThomas Jahnsjahns@dkrz.de
<p>The names of xt_idxlist and xt_idxvec are the inverse of conventional nomenclature:</p>
<ul>
<li>a vector is an ordered list of elements, but also with random access</li>
<li>a list is an ordered collection of elements, potentially with duplications</li>
</ul>
<p>so I'll rename both.</p>