Debian Codegraph @

dune/uggrid/parallel/ddd/CHANGES

raw
1 <!--
2 SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
3 SPDX-License-Identifier: LGPL-2.1-or-later
4 -->
5
6 ---------------------------
7
8 CHANGES 1.8.25 -> 1.9
9 ---------------------------
10 990211 kb
11 added some memory checks and initialization routines.
12 - due to C.Wieners, some neuralgic parts of the
13 code have been equipped with assert and memset
14 calls in order to find possible serious application bugs
15 easier in future.
16 - GetIFMem in if/ifuse.c.
17 - NewCoupling in mgr/cplmgr.c.
18 ---------------------------
19
20 CHANGES 1.8.24 -> 1.8.25
21 ---------------------------
22 990202 kb
23 fixed bug which lead to PrioBegin/End error.
24 - the std-interface was not sorted correctly, because of
25 invalid initialization of the CPLDIR-flags. This is fixed now.
26 - added some debug info in prio/pcmds.c
27 ---------------------------
28
29 CHANGES 1.8.23 -> 1.8.24
30 ---------------------------
31 980922 kb
32 new option OPT_CPLMGR_USE_FREELIST.
33 - if this option is set to OPT_ON (default), the Coupling-Manager
34 will allocate all COUPLING-structs in segmented lists with
35 freelist management. For applications which use a simple malloc-
36 style MemMgr interface, this will lead to more performance due
37 to allocation of larger blocks and avoidance of many malloc/free
38 operations. If the application itself implements a powerful
39 memory management, this option could be turned to OPT_OFF.
40 Then, each COUPLING struct is allocated/freed separately.
41 ---------------------------
42
43 CHANGES 1.8.22 -> 1.8.23
44 ---------------------------
45 980909 kb
46 new DDD module 'Prio'.
47 - when using the Xfer-module just for changing the priorities
48 of distributed objects, a lot of communication and computation
49 overhead is generated, which is not necessary due to the
50 lack of information propagation.
51 - the new Prio-environment provides two functions
52 DDD_PrioBegin()/DDD_PrioEnd() for starting and ending a
53 Prio-environment and a third function DDD_PrioChange()
54 for issuing PrioChange-commands.
55 - this environment is able to communicate the changed priorities
56 directly via communication using the standard interface.
57 980720 kb
58 Renumbered error codes in TypeMgr.
59 - this update serves as a preparation for a more solid error
60 code numbering scheme with well-documented errors. This is
61 the beginning.
62 980707 kb
63 DDD_XferEnd will try to recover.
64 - using the exception-capability of DDD_Notify, XferEnd will
65 try to give up if it cannot allocate necessary resources
66 (most of all, memory allocation). If a certain point
67 of-no-return hasn't been reached in the course of the
68 Xfer-operation, the distributed algorithm is able to
69 shutdown safely without changing the DDD data structures.
70 This might be used to recover from a low-memory situation
71 by speculative XferEnds.
72 980707 kb
73 DDD_Notify has exception-capability.
74 - during the global communication in Notify, each processor
75 may initiate a global exception message instead of taking
76 part in a normal Notify-operation. The DDD_Notify() call
77 won't return the number of receive messages for the local
78 processors, but will return the largest exception number
79 instead (with changed sign).
80 980706 kb
81 memory-intensive DDD functions can return success codes now.
82 - NOTE: the API has changed! DDD_XferEnd, DDD_JoinEnd and
83 DDD_IdentifyEnd are returning a DDD_RET code now.
84 - in future versions DDD will become more robust in terms
85 of memory shortage. Up to now, the functions mentioned
86 above are throwing corefiles on memory shortage, this
87 will be replaced by returning DDD_RET_ERROR_NOMEM.
88 ---------------------------
89
90 CHANGES 1.8.21 -> 1.8.22
91 ---------------------------
92 980702 kb
93 reduced overall memory requirements.
94 - DDD_PROC is now an 'unsigned short'.
95 - Xfer-Unpack needs less memory due to casting of PRIO and
96 ATTR values to char in NewCpl-structures.
97 ---------------------------
98
99 CHANGES 1.8.20 -> 1.8.21
100 ---------------------------
101 980527 kb
102 bugfix in Ident memory handling.
103 ---------------------------
104
105 CHANGES 1.8.19 -> 1.8.20
106 ---------------------------
107 980525 kb
108 changed memory handling in Ident.
109 - similar to changes in Xfer module for ddd-1.8.18, the
110 Identify-module memory management has been revised.
111 Memory allocation and freeing may now be done more
112 specifically.
113 ---------------------------
114
115 CHANGES 1.8.18 -> 1.8.19
116 ---------------------------
117 980519 kb
118 bugfix in memory handling.
119 - the send-message buffers during ConsCheck where allocated
120 from a wrong source.
121 980518 kb
122 reduced size of Xfer-messages.
123 - during Xfer, message buffers are allocated for send and
124 receive messages. The size of these message buffers (and
125 the size of the transferred messages) depend mostly on the
126 number of objects which must be transferred. Each message
127 contains an ObjectTable, which serves as a directory for
128 the objects contained in that messages. This object table
129 has been reduced by about 12%.
130 ---------------------------
131
132 CHANGES 1.8.17 -> 1.8.18
133 ---------------------------
134 980514 kb
135 complete redesign of memory handling.
136 - memory handling, esp. during DDD_XferEnd() is done more specifically,
137 now. Each call to AllocTMEM and FreeTMEM is given an additional
138 parameter 'kind', which tells the memory manager what kind of
139 memory is allocated. A simple memory manager can ignore this and
140 call malloc() and free().
141 - Also module Join has been changed accordingly.
142 - NOTE: the memory manager (MemMgr) interface has changed, some calls
143 have more parameters!
144 ---------------------------
145
146 CHANGES 1.8.16 -> 1.8.17
147 ---------------------------
148 980505 kb
149 bugfix in DDD_XferObjIsResent().
150 ---------------------------
151
152 CHANGES 1.8.15 -> 1.8.16
153 ---------------------------
154 980427 kb
155 added new error control feature for Ident-module.
156 - when using MPI on workstations, messages with different lengths
157 can be sent and received. This results in quiet error situations,
158 when the number of Identify-calls on pairs of processors is not
159 equal. Now, the overall length of each message is sent as first
160 data item, so that DDD can check this value and abort with an
161 error, if necessary. Thus, many errors might be detected now
162 which could previously lead to a lot of follow-up errors.
163 980427 kb
164 additions for CPP_FRONTEND.
165 - now, the c++demo application is running with DDD and CPP_FRONTEND.
166 - the calling of DDD Handlers has been reworked. Virtual member
167 function calls are avoided completely (an option to use them
168 will be implemented in the future).
169 - the application programmer has to provide a DELETE-handler for
170 each class derived from DDD_Object, which only contains a
171 'delete this'. This should be automated in future versions.
172 ---------------------------
173
174 CHANGES 1.8.14 -> 1.8.15
175 ---------------------------
176 980316 kb
177 new command DDD_XferObjIsResent().
178 - returns XFER_RESENT_TRUE for objects which will receive an additional
179 copy during XferEnd() (sent by another processor).
180 ---------------------------
181
182 CHANGES 1.8.13 -> 1.8.14
183 ---------------------------
184 980313 kb
185 new command DDD_XferIsPrunedDelete().
186 - returns XFER_PRUNED_TRUE for objects with pruned DDD_XferDeleteObj()
187 commands, XFER_PRUNED_FALSE otherwise.
188 ---------------------------
189
190 CHANGES 1.8.12 -> 1.8.13
191 ---------------------------
192 980128 kb
193 new DDD module 'Join'.
194 - the Join module supports joining local object copies
195 to distributed objects by contacting one of the
196 distributed copies on an arbitrary processor which
197 owns a copy.
198 - the current implementation is preliminary, not tested
199 with large applications and not tuned for efficiency.
200 - if you are able to avoid Join and use Identify, do this.
201 Join is an expensive operation.
202 980121 kb
203 added healing-feature to ConsCheck.
204 - with the "healing"-feature, the ConsCheck is able to detect
205 local coupling inconsistencies and fix them by calling
206 AddCoupling. However, such inconsistencies indicate
207 consistency problems elsewhere (most of the cases the
208 application based on DDD), which should be fixed by
209 thinking hard and reimplement code which uses DDD
210 functionality. Therefore, the healing feature has
211 been switched off and kept in code just in case we
212 need it at some (improbable) point in future.
213 ---------------------------
214
215 CHANGES 1.8.11 -> 1.8.12
216 ---------------------------
217 971024 kb
218 improved memory handling.
219 - use compiler-switch XferMemFromHeap to instruct the Xfer
220 module using the MemMgr's Heap-functions (Mark/Alloc/Release)
221 to get memory for receive buffers and other data.
222 Note: this feature is not yet in its final state and will
223 be extended in future versions.
224 - use compiler-switch ConsMemFromHeap to instruct the ConsCheck
225 module using the MemMgr's Heap-functions (Mark/Alloc/Release)
226 to get memory for receive buffers and other data.
227 Note: this feature is not yet in its final state and will
228 be extended in future versions.
229 971023 kb
230 xfer more efficient, in space and time.
231 - used new container classes for several data structures in
232 Xfer.
233 - now, DDD_XferCopyObj calls will be merged on the fly, as
234 a result the XFERCOPY-handlers will only be called if the
235 corresponding call to DDD_XferCopyObj is either new or
236 wins against an existing call with respect to priority-
237 merge.
238 971020 kb
239 new base level of container class data structures.
240 - introduced new object-oriented style via C preprocessor.
241 implemented several efficient container classes with
242 this style.
243 ---------------------------
244
245 CHANGES 1.8.10 -> 1.8.11
246 ---------------------------
247 971010 kb
248 added error checks for various calls to PPIF.
249 - in several modules, PPIF functions had been called
250 without checking for error conditions afterwards.
251 Now, error checking has been added which will HARD_EXIT
252 after PPIF reports an error.
253 971010 kb
254 fixed bug ('semantical problem') in xfer/unpack.c.
255 - during calls to AddDataScatter and other handlers,
256 the order of calls for two or more incoming copies of one
257 distributed DDD object could be: 1.XFER_REJECT, 2.XFER_NEW ...
258 This was wrong, because the first handler call should be
259 for the XFER_NEW object, the following calls for the
260 XFER_REJECT objects. This has been fixed now for all handlers
261 which get a 'newness'-argument.
262 971009 kb
263 added documentation.
264 - using the inline documentation and much additional texts
265 (which are currently not in the distribution), a postscript
266 file is generated (doc/ddd_doc.ps). This contains the
267 reference manual, user's manual, tutorial, error-list,
268 and implementation details ('inside ddd'). Currently,
269 only the reference manual is in a fairly advanced state.
270 971009 kb
271 added DDD_XferWithAddData().
272 - this function returns a boolean value telling the caller
273 if additional data will be really sent or just discarded.
274 ---------------------------
275
276 CHANGES 1.8.9 -> 1.8.10
277 ---------------------------
278 971007 kb
279 Global coupling-table is now enlarged dynamically.
280 - the upper limit MAX_CPL has been removed. each time the maximal
281 number of couplings on a processor is reached, its coupling table
282 (and depending on this, other tables) is doubled in size. this is
283 to make DDD more robust also on very, very big machines.
284 971007 kb
285 LowComm is now able to handle low-memory situations.
286 - if LowComm cannot get enough memory from the MemMgr-layer,
287 it will try now to wait for running messages and free their
288 send buffers. After that, enough memory should be available.
289 The Xfer-implementation had to be changed slightly to use this
290 feature.
291 ---------------------------
292
293 CHANGES 1.8.8 -> 1.8.9
294 ---------------------------
295 970909 kb
296 added inline documentation.
297 - in some later version, the DDD sources will be completely
298 documented by inline descriptions in DOC++ (ZIB Berlin)
299 style. This is work in progress.
300 970908 kb
301 removed need for (very) large object table.
302 - in all earlier versions, DDD maintained on each processor
303 a pointer array referencing all DDD objects on that processor.
304 the need for these arrays has been removed in 1.8.9.
305 Compile-switch WithFullObjectTable may be used to
306 enable the large object tables again, this might be useful
307 for debugging.
308 Without this compile-switch being set, DDD will _not_ have
309 any knowledge about objects which do not have coupling
310 (i.e. local objects). When copies of such objects are created,
311 or those objects are involved in Identify-procedures, they
312 will be put under DDD control. Otherwise, the application
313 layer has to maintain the storage for these objects.
314 ---------------------------
315
316 CHANGES 1.8.7 -> 1.8.8
317 ---------------------------
318 970704 kb
319 bugfix in Xfer module.
320 - reference-merging does now work also with rule XFER-C2 in all situations.
321 ---------------------------
322
323 CHANGES 1.8.6 -> 1.8.7
324 ---------------------------
325 970702 kb
326 bugfix in Interface module.
327 - when a processor moved all its objects to another proc,
328 in versions before 1.8.7 the interface representation
329 hasn't been deleted. this is fixed now.
330 970702 kb
331 bugfix in Identify module.
332 - the changes of 970528 seem to work correctly now.
333 did some software reorganisation.
334 ---------------------------
335
336 CHANGES 1.8.5 -> 1.8.6
337 ---------------------------
338 970701 kb
339 added check for PPIF initialization in DDD_Init().
340 970528 kb
341 reinvented STAT statistical evaluation.
342 - the DDD_StatXXX functionality will be used
343 extensively in future versions in order to provide
344 an interface for performance measuring and other
345 accounting information from DDD to application level.
346 970528 kb
347 tuning in Identify module.
348 - replaced sorting of array with big entries by sorting
349 of array with pointers to big entries. better performance
350 on systems with poor memcpy-implementation.
351 - NOTE: this can lead to errors on complicated identification
352 tasks. (normally it should work, however). keep that in mind.
353 970417 kb
354 added DDD_TYPE_BY_HANDLER for EL_OBJPTR in TypeDefine.
355 - normally, for EL_OBJPTR defined during TypeDefine
356 the DDD_TYPE of the referenced object has to be given.
357 - now, one can replace this argument (a DDD_TYPE) by the
358 constant DDD_TYPE_BY_HANDLER, and an additional argument
359 which is a function pointer to a handler function of the
360 type HandlerGetRefType, i.e. (see ddd.h)
361 DDD_TYPE (*HandlerGetRefType) (DDD_OBJ o1, DDD_OBJ o2)
362 - DDD will call this handler whenever it needs to evaluate
363 the referenced type. then, o1 is the object containing
364 the reference, o2 is the referenced object (for which the
365 type must be given). the function must return the actual
366 type of o2.
367 - when defining arrays of EL_OBJPTR, the handler function
368 will be called for each reference in turn.
369 970417 kb
370 change in priority consistency during xfer.
371 - when a local object is XFER_UPGRADEd during xfer/unpack,
372 its priority has been set immediately (until 1.8.5).
373 - for calling the user-defined handler SETPRIORITY,
374 the old prio-value had been restored into the object's
375 DDD_HEADER; after the call to the handler (if any),
376 the new priority value was inserted again.
377 - from 1.8.6 on: the priority isn't set immediately, but only
378 after the call to SETPRIORITY. This implements the following
379 priority consistency model: BEFORE AND DURING the call
380 to the SETPRIORITY handler, the object has its old priority.
381 AFTER calling the SETPRIORITY handler, the object has its
382 new priority.
383 970416 kb
384 fixed some bugs found by evaluation version of Purify.
385 ---------------------------
386
387 CHANGES 1.8.4 -> 1.8.5
388 ---------------------------
389 970414 kb
390 fixed serious bug in xfer/unpack. NEVER USE 1.8.4!
391 970411 kb
392 added new option OPT_XFER_PRUNE_DELETE.
393 - with this option set to OPT_ON, DelCmds during transfer
394 will discarded, if a XferCopyObj command for the same
395 distributed object exists. Therefore, the object will
396 not be deleted and created afterwards.
397 - the priority merging of the two objects will be as given
398 in the specification, i.e., the new object will be accepted
399 disregarding its priority.
400 970327 kb
401 fixed serious bug in xfer/unpack.c.
402 - bug could occur with procs>=4
403 - now coupling consistency should work properly.
404 - efficiency (runtime, message size and storage) is not quite
405 clear for large problems. TODO: this must be checked.
406 ---------------------------
407
408 CHANGES 1.8.3 -> 1.8.4
409 ---------------------------
410 970310 kb
411 additional options OPT_INFO_XFER, with values XFER_SHOW_xxx.
412 - can be used to control memory allocation in Xfer module.
413 970310 kb
414 additional error messages in ident.c.
415 970310 kb
416 bugfix in basic/topo.c (error occurred with procs>64).
417 ---------------------------
418
419 CHANGES 1.8.2 -> 1.8.3
420 ---------------------------
421 970306 kb
422 increased MAX_TRIES timeout value to 50M.
423 970305 kb
424 added CtrlTimeouts(Detailed) switch in if/if.h.
425 - this may be used for checking the interface timeout values.
426 - CtrlTimeouts displays the timeout value after each IF communication
427 (on each proc one line for send/receive)
428 - CtrlTimeoutsDetailed displays the timeout values for each
429 message during a IF communication (on each proc one line for
430 send/receive of any message)
431 ---------------------------
432
433 CHANGES 1.8.1 -> 1.8.2
434 ---------------------------
435 970304 kb
436 increased size of notify buffer to 2*(n*(n-1)/2) (for message send/receive).
437 ---------------------------
438
439 CHANGES 1.8 -> 1.8.1
440 ---------------------------
441 970303 kb
442 added new function DDD_IFInfoMemory().
443 - this function returns the number of bytes used for representing
444 a given DDD interface.
445 - available in all FRONTENDs.
446 970303 kb
447 cleanup of memory management.
448 - removed some memory leaks.
449 - improved performance by introducing segments of memory instead
450 of doing many, many alloc/free requests. this was done in
451 xfer/sll.ct (for auxiliary data structures in Xfer), and in
452 xfer/supp.c (for AddData structures).
453 - memory for DDD interfaces is constructed exactly as large as needed.
454 up to now, memory has been wasted (esp. when there were many DDD-types
455 as distributed objects). memory usage for interfaces will be
456 about factor 6-8 smaller now.
457 970217 kb
458 removed lots of warnings with C++ on SGI.
459 ---------------------------
460
461 CHANGES 1.7.8 -> 1.8
462 ---------------------------
463 970217 kb
464 started to C++-ize PPIF and extended functionality.
465 970212 kb
466 added powerful memory-management debugging tool.
467 - some switches (CheckPMEM, CheckAMEM, CheckTMEM) can be
468 set at compile time in dddi.h in order to control the
469 memory usage of the DDD-library. each allocated chunk
470 will be sizeof(size_t) bigger, in the additional section
471 the size of the allocated memory is stored. this is used
472 for printing of MALL and FREE output.
473 970212 kb
474 revised handler handling. :-)
475 - now, for each DDD-handler there is a corresponding
476 SetHandler function (e.g., DDD_SetHandlerUPDATE for
477 UPDATE-handler). The first argument of each handler
478 function is the DDD_TYPE for which the new handler
479 should be registered, the second argument is a
480 pointer to the handler function itself (e.g., of
481 type HandlerUPDATE).
482 - in ddd.h there is a list of prototypes for all handlers,
483 i.e., now the compiler can do static type checking for
484 handler functions and their parameters.
485 - the old functionality DDD_HandlerRegister with variable
486 argument list is supported for downward compatibility.
487 970212 kb
488 introduced OLDSTYLE-warnings.
489 - for functions which are supported for downward
490 compatibility only and which will be removed in some
491 future version, a warning is issued each time the
492 function is called.
493 - additionally, some hints are added how to upgrade to new
494 version.
495 - with DDD_OPTION OPT_WARNING_OLDSTYLE these warnings can
496 be switched off.
497 970212 kb
498 revised handler calls in F_FRONTEND.
499 - now all relevant handlers are called also in F_FRONTEND
500 version (with call-by-reference parameters).
501 970211 kb
502 implemented object-oriented CPP_FRONTEND prototype.
503 - supports C-style objects (as structs or classes) and
504 Fortran-style objects (as collections of distributed
505 arrays).
506 - implementation as object-oriented class hierarchy encapsulated
507 the ANSI C implementation of DDD.
508 - class DDD_Library with a single instance represents
509 the DDD library.
510 - class DDD_Object represents a distributed object.
511 - class DDD_IndexObject represents a object stored in
512 array-like manner.
513 - template classes DDD_ObjectOf<T> and DDD_IndexObjectOf<T>
514 may be used for very elegant parallelization of sequential
515 object-oriented codes.
516 - class DDD_Interface encapsulates a DDD interface, communication
517 can be done via DDD_GatherScatter-objects.
518 - now, C_FRONTEND, F_FRONTEND and CPP_FRONTEND in one single
519 code.
520 - see coming documentation and demo examples for using CPP_FRONTEND.
521 ---------------------------
522
523 CHANGES 1.7.7 -> 1.7.8
524 ---------------------------
525 970205 kb
526 added many USER_DATA streams feature.
527 - all IDs in interval [DDD_USER_DATA, DDD_USER_DATA_MAX] may
528 be used for sending byte streams as AddData.
529 970204 kb
530 started with CPP_FRONTEND, designed some classes in ddd.h.
531 970204 kb
532 revision for global ID construction.
533 - the definition of MAX_PROCBITS_IN_GID has been moved to dddi.h.
534 this gives the number of bits inside each global ID.
535 - the number of bits for the processor number inside the global ID
536 is a limit for the maximum number of processors. now this number
537 is checked in DDD_Init() with error message and exit.
538 - the overflow of global IDs is checked and DDD is exited with an
539 error message. this will occur after 2^(32-MAX_PROCBITS_IN_GID) calls
540 to DDD_HdrConstructor().
541 ---------------------------
542
543 CHANGES 1.7.6 -> 1.7.7
544 ---------------------------
545 970131 kb
546 new element type EL_GBITS.
547 - with EL_GBITS, one can define components of DDD-types bitwise.
548 1=GDATA, 0=LDATA. for DDD_TypeDefine, a line for defining a
549 bitwise element looks like this:
550 EL_GBITS, &a, sizeof(a), bitarray
551 where a is a structure component, sizeof(a) its size, and
552 bitarray a character-array (unsigned char *) with length
553 sizeof(a), where the bits are set according to GDATA or LDATA
554 property.
555 - not implemented for F_FRONTEND.
556 ---------------------------
557
558 CHANGES 1.7.5 -> 1.7.6
559 ---------------------------
560 970129 kb
561 new interface for general PriorityMerge.
562 - default for merging of priorities is MAXIMUM.
563 - a new default can be set by DDD_PrioMergeDefault()
564 - special exceptions can be introduced by DDD_PrioMergeDefine()
565 - the current setting is displayed by DDD_PrioMergeDisplay()
566 - the PrioMerge operation might be tested from application level
567 via DDD_PrioMerge().
568 - all PrioMerge operations work with DDD_TYPE as first argument,
569 i.e., one can define arbitrary PrioMerge logic for each DDD_TYPE.
570 - the Xfer-Module has been adapted so that it supports the general
571 PrioMerge settings.
572 970129 kb
573 replaced all exit(1) calls by macro call HARD_EXIT.
574 - the current default for HARD_EXIT is assert(0), thus, one
575 will get a core file after every DDD error.
576 - later (in production versions) one can replace this by
577 simple exit(1) or similar.
578 970129 kb
579 added new parameter newness to calls of scatter-handlers.
580 - HANDLER_XFERSCATTER and HANDLER_XFERSCATTERX get an additional
581 parameter 'newness', which is one of { XFER_REJECT, XFER_UPGRADE,
582 XFER_NEW }, depending on an incoming objects status.
583 - this should be documented in RefMan.
584 NOTE: changing of XFERSCATTER parameterlist in applications necessary!
585 ---------------------------
586
587 CHANGES 1.7.4 -> 1.7.5
588 ---------------------------
589 970128 kb
590 added OPT_INFO_XFER.
591 - this runtime option shows additional (statistical)
592 information during XferBegin/XferEnd. default is OPT_OFF.
593 970128 kb
594 changed interface display functions and added some output.
595 - DDD_IFDisplay now takes an argument DDD_IF in order
596 to display only one interface.
597 - DDD_IFDisplayAll is a new function displaying all
598 interfaces (formerly DDD_IFDisplay)
599 - DDD_IFSetName allows to define a textual description for
600 interfaces, which is displayed by DDD_IFDisplay and
601 DDD_IFDisplayAll.
602 NOTE: this change requires renaming of function DDD_IFDisplay in
603 all applications!
604 ---------------------------
605
606 CHANGES 1.7.3 -> 1.7.4
607 ---------------------------
608 970124 kb
609 fixed bug in interface communication.
610 - IF_Axxx (i.e. communication by attribute) crashed when
611 IF-parts without objects existed.
612 970124 kb
613 increased size of NOTIFY-table.
614 ---------------------------
615
616 CHANGES 1.7.2 -> 1.7.3
617 ---------------------------
618 970121 kb
619 changed order of handler calls in xfer-unpack implementation.
620 - now MKCONS handler gets second parameter 'newness'.
621 XFER_UPGRADE for objects upgraded according RULE C3.
622 XFER_NEW for new objects.
623 - this should be documented in RefMan.
624 NOTE: changing of MKCONS parameterlist in applications necessary!
625 ---------------------------
626
627 CHANGES 1.7.1 -> 1.7.2
628 ---------------------------
629 970115 kb
630 changed xfer-unpack implementation.
631 - up to ddd-1.7.1, the unpack-handlers (i.e. UPDATE, XFERSCATTER,
632 SETPRIORITY, OBJMKCONS) where called for each incoming message
633 in turn. now, all UPDATE handlers are called, then all XFERSCATTER
634 handlers and so on (SETPRIORITY, OBJMKCONS).
635 - this is a temporary solution. in later versions, the handler
636 calls will be reworked; efficiency will be improved by cleaning
637 up the loop structure in xfer-unpack.
638 ---------------------------
639
640 CHANGES 1.7 -> 1.7.1
641 ---------------------------
642 970110 kb
643 re-implementation of current interface functionality.
644 - only one implementation for 24 DDD_IFxxx interface functions
645 (via templates).
646 - the following possibilities can be used now:
647 { C_FRONTEND, F_FRONTEND} x
648 { Exchange, Oneway, ExecLocal} x
649 { one DDD_ATTR, all DDD_ATTRs } x
650 { normal gather/scatter-params, extended gather/scatter-params }
651 - the next step will be implementation of maskable DDD_ATTRs.
652 970110 kb
653 standard interface cannot be used for communication.
654 - user must define an interface in order to communicate.
655 the standard interface is only used for creating
656 the user interfaces and cannot be used with DDD_IF..
657 commands anymore.
658 - object shortcuts will not be computed for the standard
659 interface.
660 970110 kb
661 added second call to handler HANDLER_SETPRIORITY.
662 - now the SETPRIORITY-handler is called when a local
663 object's priority is set by DDD_PrioritySet() and when
664 an object's priority is upgraded due to an incoming object
665 with same gid, but higher (or equal) priority.
666 - this feature is a temporary setting. in some later version,
667 we will rework all handler calls during xfer-unpack in order
668 to clean up "historical" developments.
669 ---------------------------
670
671 CHANGES 1.6.10 -> 1.7
672 ---------------------------
673 961220 kb
674 added option OPT_WARNING_REF_COLLISION, with default OPT_ON.
675 - each EL_OBJPTR (i.e. each reference) inside a DDD object
676 must be NULL_REF or a pointer to a valid DDD-object.
677 when two or more local objects of one distributed object
678 exist, each reference element must contain either NULL_REF or
679 a reference to THE SAME valid DDD-object. if this is not the
680 case, a warning 'reference collision' will be issued by DDD.
681 this option may be used for switching this warning off, which
682 might be dangerous due to possible data inconsistencies.
683 961219 kb
684 switched on merge-mode for xfer-unpack.
685 - now references of
686 incoming objects and objects already on the local processor
687 are merged.
688 ---------------------------
689
690 CHANGES 1.6.9 -> 1.6.10
691 ---------------------------
692 961209 kb
693 new function DDD_InfoNCopies().
694 - returns number of copies of a local object. The local object itself
695 is not included.
696 961128 kb
697 integrated changes from F_FRONTEND branch.
698 - now F_FRONTEND is available with reference conversion,
699 part of the interface communication functions and tested
700 with 1-2 simple applications.
701 updated README, arch and ppif.
702 ---------------------------
703
704 CHANGES 1.6.8 -> 1.6.9
705 ---------------------------
706 961128 kb
707 bugfixes in Identify-module.
708 ---------------------------
709
710 CHANGES 1.6.7 -> 1.6.8
711 ---------------------------
712 961127 kb
713 changed prototype of DDD_IFDefine.
714 - second parameter is DDD_TYPE*, forth and sixth parameters
715 are DDD_PRIO*. This change requires changes in all applications.
716 changed value of DDD_USER_DATA to positive value.
717 - also usage of DDD_USER_DATA in Xfer-module has been adapted.
718 still more functionality for Identify-module.
719 - now OPT_IDENTIFY_MODE may be set to two different values:
720 - in IDMODE_LISTS, the order of Identify-command issuing is
721 relevant, i.e., tupel1=(5,3) and tupel2(3,5) are different.
722 - in IDMODE_SETS, the order of Identify-commands in each tuple
723 is ignored; the IdentifyModule itself reorders each tupel's
724 entries. then, tupel1 and tupel2 from the above example are
725 the same.
726 961126 kb
727 additional functionality for Identify-module.
728 - in calls to DDD_IdentifyObject, now objects can be used as
729 identifiers which are also identified in the current
730 IdentifyBegin/IdentifyEnd step. I.e., identification can use
731 hierarchical IdentifyObject-calls, objects can be used as identifiers
732 which itself haven't been identified before!
733 - communication has been tuned, now REALLY only gid and prio is
734 sent for each object which must be identified.
735 - lots of debugging levels introduced.
736 ---------------------------
737
738 CHANGES 1.6.6 -> 1.6.7
739 ---------------------------
740 961026 kb
741 some changes due to comments from Klaus-Dieter Oertel.
742 - changed typedefs for DDD_PRIO, DDD_ATTR etc to unsigned int
743 - added functions to encapsulate PPIF's global variables me,
744 master, procs (DDD_InfoMe etc)
745 961016 kb
746 added changes from ug-ddd-version into actual ddd-repository.
747 - some new interface functions, an interface checker
748 - moved HANDLER_PRIORITYSET from prio.c into xfer.c
749 - new functions DDD_SearchHdr and DDD_InfoIsLocal
750 961019 kb
751 added PITFALLS file to collect common errors by DDD users.
752 ---------------------------
753
754 CHANGES 1.6.5 -> 1.6.6
755 ---------------------------
756 960906 kb
757 added consistent object deletion during xfer (from HANDLER_DELETE).
758 added HANDLER_SETPRIORITY.
759 changes for NEC-SX4 compilation.
760 added new functions DDD_IFExecLocal and DDD_IFAExecLocal.
761 960905 kb
762 xfer-module completely rewritten.
763 - complete coupling consistency with 2 communication phases.
764 - spread-communication of prior versions had been removed.
765 - xfer-module now implements the written xfer-specification.
766 - dddic checked approx. 100000 testcases for xfer of one
767 distributed object, without errors.
768 - data structures are based on templates now, which implement
769 linked list with free lists.
770 - abstractions have been worked out more carefully.
771 - testing was successful for fedemo.
772 960813 kb
773 cplmsg.c, added new information about coupling consistency during
774 transfer.
775 960722 kb
776 lowcomm.c, new low communication layer.
777 - lowcomm supports messages consisting of several tables and/or
778 data chunks. it also encapsulates n-to-n-messaging; it notifies
779 the receiving procs, allocates message buffers, computes
780 message sizes.
781 - reworked xfer-module and ConsCheck in order to use the new
782 lowcomm layer. therefore, these modules have been restructured
783 completely.
784 960715 kb
785 topo.c, reworked channel handling. code for using DDD_GetChannels()
786 is much smaller now.
787 960712 kb
788 introduced general message structure, now Notify() doesn't rely on
789 special messages for Xfer, Spread, Cons etc anymore.
790 960703 kb
791 xfer, split XferInfo-list into two, one for objects and one for
792 couplings.
793 ---------------------------
794
795 CHANGES 1.6.4 -> 1.6.5
796 ---------------------------
797 960618 kb
798 restructured Makefile.ddd, in order to establish new structure
799 of arch/ppif/ddd and applications.
800 ---------------------------
801
802 CHANGES 1.6.3 -> 1.6.4
803 ---------------------------
804 960611 kb
805 typemgr.c, changed behaviour on errors.
806 - now every error during TypeMgr operations leads to exit(1)
807 of program.
808 960610 kb
809 pack.c/unpack.c, enabled runtime activation of xfer debug output.
810 - the contents of messages being sent/received during xfer
811 may be printed out by activating DDD option OPT_DEBUG_XFERMESGS.
812 960607 kb
813 added object size testing to XferCopyObjX and ObjGet.
814 - via DDD options OPT_WARNING_SMALLSIZE and OPT_WARNING_VARSIZE_OBJ
815 issuing of warnings on size!=desc->size events can be controlled.
816 960607 kb
817 xfer.c, added handler HANDLER_DELETE for different way of object deletion.
818 - HANDLER_DELETE is an alternative way of deleting objects; the
819 necessary DDD_HdrDestructor must be called by the applications
820 HANDLER_DELETE handler.
821 - the handler definition in ddd.h had been reworked in order to
822 get more independent of future additions to handler list.
823 960604 kb
824 fixed bug in compiler.h.
825 - alignment entry for __INDIGO__ was 4 (8 is the correct value)
826 ---------------------------
827
828 CHANGES 1.6.2 -> 1.6.3
829 ---------------------------
830 960528 kb
831 integrated changes for F_FRONTEND.
832 - this includes all work by Jens Boenisch, together with some
833 integration work and debugging by kb. simple test programs
834 in fortran with ddd are working now.
835 - the main point NOT implemented in this version is handling
836 of 'pointers', i.e., how f77-indices are translated into
837 ddd references and globalized/localized during xfer.
838 this work will be done during the next implementation phase
839 of F_FRONTEND.
840 - main features working right now: TypeMgr, ObjMgr, IFDefine,
841 Xfer without references.
842 ---------------------------
843
844 CHANGES 1.6.1 -> 1.6.2
845 ---------------------------
846 960512 kb
847 unpack.c, complete rewrite
848 - LocalObjectsList() caused a serious efficiency problem. it was called
849 several times during each transfer. therefore, the complexity of xfer
850 was #local_objects*log(#local_objects)*C, where C is a (not very small)
851 constant.
852 in order to provide an efficient solution, the unpack-module has been
853 rewritten completely. now a list of new (incoming) objects is constructed
854 an sorted; this lead to a complexity which is independent of
855 #local_objects, and is depending only on the number of objects
856 in interface, instead.
857 debugging and testing had been done quite thoroughly.
858 ---------------------------
859
860 CHANGES 1.6 -> 1.6.1
861 ---------------------------
862 960507 kb
863 ifcreate.c, improved memory complexity
864 - due to bad estimates of memory needed for representing the
865 interfaces (as lists of coupling pointers), mmuch memory had
866 had been wasted at runtime (about 0.5MB per interface and processor).
867 this has been fixed by maintaining a coupling counter per processor,
868 which can be used to compute the exact size of the standard interface
869 and from this the maximum size for each defined interface. these sizes
870 are usually much smaller than the rough estimates before this fix.
871 ---------------------------
872
873 CHANGES 1.5 -> 1.6
874 ---------------------------
875 960402 kb
876 typemgr.c, added EL_CONTINUE feature
877 - DDD_TypeDefine() calls may be ended by EL_CONTINUE now (instead of
878 EL_END), which ends up with partially defined DDD_TYPEs.
879 these partially defined DDD_TYPEs may be defined further by
880 more calls to DDD_TypeDefine().
881 ---------------------------
882 960209 kb
883 ident.c, fixed two bugs:
884 - VChannel allocation was blocking in some cases;
885 fix: replaced VChannel allocation by GetChannel() from topo.c
886 - asynchronous info functions didn't cooperate with get_SHMEM-ppif for T3D.
887 (SHMEM-ppif had stronger synchronization requirements than expected).
888 fix: sorted Info-functions, first poll receives, then poll sends.
889 ---------------------------
890 960207 kb
891 unpack.c, fixed bug
892 - when 0-pointer was unpacked, the HDR2OBJ conversion was called.
893 this is not valid for 0-pointers.
894 fix: inserted if-statement.
895 ---------------------------
896 960110 kb
897 renamed main.c to ddd.c.
898 ---------------------------
899
900 CHANGES 1.4 -> 1.5
901 ---------------------------
902 960110 kb
903 objmgr.c, second complete rewrite
904 - reorganized DDD_HDR constructors
905 - introduced 3 interfaces for object construction/destruction
906 ---------------------------
907 960113 kb
908 ifuse.c, removed bug in DDD_IFOneway()
909 ---------------------------
910 960117 kb
911 IF-module
912 - created new files ifcmds.c and ifobjsc.c
913 - introduced obj-shortcut-tables for quick reference during
914 interface-communication
915 - created shortcut-table-invalidation/validation-interface
916 ---------------------------
917
918 CHANGES 1.3 -> 1.4
919 ---------------------------
920 951103 kb
921 DDD_StructRegister
922 - second argument (ddd_hdr) vanished
923 - use EL_DDDHDR instead (in element list)
924 - possibility to recursively register known DDD_TYPEs,
925 via entering their id in the EL_xxx field
926 - better error checking and reporting
927 - DDD_HDR itself is a DDD-object (DDD_TYPE=0)
928 - C++ support: inheritance of DDD-objects is possible,
929 virtual inheritance gives a warning (nty)
930 - added mask for easy and efficient object copying
931 - restructured code (C++style)
932 ---------------------------
933 951103 kb
934 objmgr.c, complete rewrite.
935 - now object-oriented style is supported:
936 constructors, new-operators etc
937 - handler interface rewritten
938 - downward compatibility with V1.3:
939 DDD_ObjGet still supported
940 - CopyConstructor uses copymask from DDD_StructRegister
941 - changed definition of handlers (and their names, just
942 to be sure)
943 ---------------------------
944 951106 kb
945 main.c, changed parameters of DDD_Init to
946 void DDD_Init (int *argcp, char ***argvp)
947 for compatibility with MPI and similar parallel
948 programming models. Involves changes of parameters
949 of InitPPIF and all its current implementations.
950 ---------------------------
951 951116 kb
952 created typemgr.c (from main.c)
953 - removed DDD_StructRegister, DDD_StructDisplay.
954 - created new TypeMgr interface DDD_TypeDeclare(),
955 DDD_TypeDefine(), DDD_TypeDisplay().
956 - when defining types, the targets for all references
957 (EL_OBJPTR) have to be specified
958 ---------------------------
959 951117 kb
960 arbitrary DDD_HEADER offsets
961 - from now on DDD_HEADER may have arbitrary offset
962 for each DDD_TYPE
963 ---------------------------
964 951121 kb
965 changed OBJ_DESCR to TYPE_DESC, EL_DESCR to ELEM_DESC,
966 objstruct to theTypeDefs
967 ---------------------------
968 951122 kb
969 renamed DDD_DisplayIF() to DDD_IFDisplay()
970 ---------------------------
971