* Make JniException a runtime exception, so that there is no need to
declare the fact that you may encounter such a beast. I guess that
nobody will ever want to survive such error.
- Ruby Bindings: create it
- * That's new and great, you should try it out.
- Kinda the same functionalities than Java bindings
+ * Create specific errors for each MSG case of failure:
+ host failure, transfer failure, timeout, task cancelled
+ Ruby and Lua Bindings: create them
+ * That's new and great, you should try them out.
+ Same functionalities than Java bindings, only even less polished
SimDag:
* Kill the useless "rate" argument of SD_task_get_execution_time()
Everyone used to provide -1 as a value, it was not used, and the
* Kill the MSG_paje_output() function. It's a noop since 2 years.
* Kill MSG_WARNING and MSG_FATAL return codes: they were not used
anywere in source.
+ * Add a MSG_task_set_data() function
SIMIX:
* add a SIMIX_sem_get_capacity() function
+ * add SIMIX_action_suspend() and SIMIX_action_resume() functions
+ * Bugfix: Handle correctly the resume/suspend of processes when they
+ are blocked on semaphores.
+ SURF:
+ * Rename configuration variables to start a hierarchy:
+ o cpu_model -> cpu/model
+ o network_model -> network/model
+ o workstation_model -> workstation/model
+ * New configuration variables:
+ o network/bandwidth_factor: correction to bandwith
+ o network/latency_factor: correction to latency
+ o netwotk/weight_S: correction to the weight of competing streams
+ * Add a long description to the models, that users can see with such
+ argument on the command line: --cfg=cpu/model:help
+ * --help-models display the long description of all known models
SMPI:
* Implement MPI_Get_count, MPI_MAXLOC, MPI_MINLOC
-
-
+ XBT:
+ * config: add the ability to set a default value after registration
+ Does not override any previously set value (e.g. from cmd line)
+ * dict: allow to have integer key and data.
+ When so, you need to use the following functions
+ void xbt_dicti_set(xbt_dict_t dict, uintptr_t key, uintptr_t data);
+ uintptr_t xbt_dicti_get(xbt_dict_t dict, uintptr_t key);
+ void xbt_dicti_remove(xbt_dict_t dict, uintptr_t key);
+ In contrary to regular dicts, the key is not malloced before copy.
+ Mixing scalar and regular elements in the same dict is not tested
+ (but may work).
+ Tracing for Visualization:
+ * SimGrid is now instrumented in order to generate a trace file for
+ visualization analysis: to use it, need to compile SimGrid with the
+ "tracing" option enabled, and instrument the program using SimGrid with
+ TRACE_start, TRACE_category, TRACE_msg_set_task_category and TRACE_end
+ (among other functions).
+ * The instrumentation only traces the platform utilization for now
+ * Documentation to use the tracing functions and how to analyze the
+ traces with the Triva tool is written.
+ * More information about: SimGrid FAQ (in the section Tracing Simulations
+ for Visualization)
+
-- Da SimGrid team <simgrid-devel@lists.gforge.inria.fr>
