SimGrid (3.23) NOT RELEASED (Release Target: June 21. 2019, 15:54 UTC)
+General:
+ - Stop setting random seed with srand48() at initialization.
+ - Build option -Denable_documentation is now OFF by default.
+
XBT:
+ - New log appenders: stdout and stderr. Use stdout for xbt_help.
- Drop xbt_dict_dump.
-Fixed bugs (GH=GitHub; FM=FramaGit):
+SMPI:
+ - SMPI now reports support of MPI3.1. This does not mean SMPI supports all MPI 3 calls, but it was already the case with 2.2
+ - MPI/IO is now supported over the Storage API (no files are written or read, storage is simulated). Supported calls are all synchronous ones.
+ - MPI interface is now const correct for input parameters
+
+Model-checker:
+ - Remove option 'model-check/record': Paths are recorded in any cases now.
+
+Fixed bugs (GH=GitHub; FG=FramaGit):
+ - FG#7: simple cmake call requires doxygen
+ - FG#10: Can not use MSG_process_set_data from SMPI any more
+ - FG#11: Auto-restart actors forget their on_exit behavior
+ - GH#133: Java : a process can run on a VM even if its host is off
- GH#326: Valgrind-detected error for join() when energy plugin is activated
- - FM#10: Can not use MSG_process_set_data from SMPI any more
-
+
----------------------------------------------------------------------------
SimGrid (3.22) April 1. 2019
-The Easter Chrismas Release (this one is somewhat late).
+The Easter Christmas Release (this one is somewhat late).
Python:
- We are excited to introduce the SimGrid/S4U interface to your neighborhood
the pthread backend. It caused some weird deadlock or behavior
depending on the pthread implementation. [AL]
* Bugfix: get the exceptions raised in the simulator repport where
- and why they come from when they are not catched in time [AL, MQ]
+ and why they come from when they are not caught in time [AL, MQ]
SURF:
* Bugfix: Do repport the error when two non-connected hosts try to
* New! Exception handling with setjmp or such (code from OSSP ex) [MQ]
This deprecates the xbt_error_t mechanisms.
It modifies (simplifies) all XBT and GRAS API.
- MSG API keeps unchanged (exceptions raised by XBT are catched from
+ MSG API keeps unchanged (exceptions raised by XBT are caught from
within MSG and masked with existing error handling facilities)
SURF:
