- [08/02/2002] DaSSF 3.2.4 is
released:
Improved DML library for handling large models.
Made work with stdc++ library, including the standard templates.
Ported to Mac OS X Darwin system.
Improved data packing/unpacking support.
Added quick memory support; a common memory pool for fast allocation and deallocation.
A number of bug fixes.
- [04/16/2002] DaSSF 3.2.3 is
released:
Fixed the bug related to long long type ltime_t that appears only on some machines.
Better efficiency for handling simultaneous events on a timeline.
Fixed the bug related to DataPacked class. Thanks to Klaus Krauter.
Added QuickObject as DaSSF extension; it uses a memory pool for faster memory allocation and deallocation.
- [02/20/2002] DaSSF
3.2.2 comes with the following updates:
Fixed problems with ltime_t being long long type.
Revised support for different machine architectures and operating systems.
Better and more complicated scripts for checking system configuration and software availability.
Removed software dependencies on flex and bison.
- [01/24/2002] DaSSF
3.2.1 fixed a few mistakes:
A bug related to random number generator when random seed is reset.
User time collected for posix threads was incorrect on Irix, OSF, and Solaris platforms.
- [01/18/2002] DaSSF
3.2.0 is available. It contains many improvements over version
3.1. The following is a list of major updates included in the new
release.
Added appointment out-channel for support of zero-delay channels between timelines.
Added support for negative simulation times.
Added ProcedureContainer class for classes hosting procedures for SSF processes. The change increased flexibility of DaSSF process-oriented simulation world-view.
Completely revamped DaSSF's shared-memory management. Now it uses much more efficient memory allocators, namely Hoard from University of Texas at Austin, and Doug Lea's famous memory allocator as its backend.
A long list of bug fixes as well as miscellaneous features added for convenience.
- [08/16/2001] DaSSF
3.1.5 comes with the following fixes:
Fixed a bug that related to fixed point numbers being simulation timestamps (i.e. ltime_t).
Fixed the line shifting problem when using debuggers.
Fixed the problem with virtual procedures.
- [06/29/2001] DaSSF
3.1.4 with a major upgrade:
Fixed p4 preprocessor; relaxed some of the constraints.
Add global function: now() and current_process() for the sake of convenience.
Fixed bugs that related to vector and enumeration templates. Also, fixed the memory leak associated with global barriers.
Add enable/disable-event-copy option at configuration. Processors on shared memory can either have distinct copies of events, or share events using lock-protected reference counters. This could have impact on application with large events.
On Sun multiprocessors, the user can now use 64-bit mode. The application should be compiled with the native compiler and with Sparc V9 option.
A race condition on Irix multiprocessors has been removed.
- [05/11/2001] DaSSF
3.1.3 comes with the following upgrades:
Fixed a compilation problem on IRIX machines using the native compiler.
Reduced memory consumption for entities by reclaiming memory that is no longer used after initialization.
- [04/30/2001] DaSSF
3.1.2 fixed a major bug that is related to event cancellation of
simultaneous events.
- [04/27/2001] DaSSF
3.1.1 contains two major fixes from 3.1.0:
Redefinition of global new and delete operators to be consistent with the Standard Template Library (STL). Now, models written in DaSSF can use STL at will.
Fixed shared memory fragmentation problem.
- [04/25/2001] Dartmouth SSF 3.1.0 is available.
Version 3.1 is a major upgrade; we added new SSF API support for distributed memory platforms. In addtion to using DML scripts, the user can programmatically create models in the main function. The new version also contains important bug fixes. DaSSF 3.1 is not totally compatible with 3.0. However, models written with 3.0 can be upgraded easily to 3.1 with only minimal textual changes.
- [12/06/2000]
Dartmouth SSF 3.0 is here.
Complete revision of the application programming interface; mechanisms are added to support simulation on distributed memory environment.
DaSSF 3.0 takes the approach of having separate synchronization schemes for shared memory and distributed memory. At global level, the model is partitioned into a number of subsystems, each of which resides on a processing node and synchronizes with other subsystems via message passing. At local level, on each node, the subsystem can be further partitioned onto multiple processors of the node. The synchronization between these processors on a single node is through shared memory. Model partitioning is done automatically.
DaSSF 3.0 also includes a new mixed synchronization kernel that combines synchronous and asynchronous conservative synchronization protocols. The composition achieves better performance as it allows the kernel to tailor the synchronization mechanism ot the model being simulated. The kernel can automatically find the optimal combination of synchronous and asynchronous channels between logical processes.
- [06/16/1999] Dartmouth
SSF 1.0.5 is available.
InstantOutChannel class is provided that supports zero-time delay channel. Instead of having a positive channel delay, the user can provide a positive appointment delay. Refer to ssfext/instoutchannel.h for detail.
Also, modifications to the runtime system is made to allow global variables being shared, though there are still technical difficulties making it as fast as it was before on some of the platforms. On some platforms, it seems to be the only way to have the global variables shared using threads.
- [05/26/1999] Dartmouth SSF 1.0.4 is available
to the public.
The following is a list of major changes made since version 1.0.3. For detailed changes, refer to ChangeLog file in the root directory of DaSSF distribution.
- Directory tree structure has been changed: instead of using co-mingled headers and source files, they are now separated into include and src directories.
- File name extensions are changed from .hxx and .cxx to .h and .cc to comply with the general public.
- Class Timer, which conflicts with the timer used in ssfnet is renamed to EventTimer.
- Template classes are standardized for better usage.
