|
1 | 1 | # SST 15.1 Release Notes |
2 | 2 |
|
| 3 | +SST 15.1.1 Bug Fix Release - 2026-Jan |
| 4 | +=========================================== |
| 5 | + |
| 6 | +## SST-Core |
| 7 | +* Fixed bug that occurred in rare cases in parallel loaded simulations when checking ports on nonlocal links. |
| 8 | + |
| 9 | +SST 15.1.0 Release - 2025-Nov |
| 10 | +=========================================== |
| 11 | + |
3 | 12 | ## General |
4 | 13 | * This release has several performance improvements and bug fixes. |
5 | 14 | * The experimental debug console that allows online introspection of elements is significantly more capable. |
|
9 | 18 |
|
10 | 19 | ## Deprecation and Removal Notices |
11 | 20 | * There are no new deprecations added in this point release. The following list is copied from the 15.0 release. |
12 | | -* Use of shared TimeConverters (via pointers returned from Core API functions) is deprecated. Core APIs that accepted a `TimeConverter*` have been updated to accept a `TimeConverter` instead. |
13 | | - In SST 16.0, Core APIs that return TimeConverter pointers will be changed to return a TimeConverter instance instead. To prepare for this switch, change code to construct a local |
| 21 | +* Use of shared TimeConverters (via pointers returned from Core API functions) is deprecated. Core APIs that accepted a `TimeConverter*` have been updated to accept a `TimeConverter` instead. |
| 22 | + In SST 16.0, Core APIs that return TimeConverter pointers will be changed to return a TimeConverter instance instead. To prepare for this switch, change code to construct a local |
14 | 23 | TimeConverter instance from a returned TimeConverter pointer as shown. |
15 | 24 | ``` |
16 | 25 | // Old code |
17 | 26 | TimeConverter* tc = registerClock(...); |
18 | | - |
| 27 | +
|
19 | 28 | // New code |
20 | 29 | TimeConverter tc = registerClock(...); |
21 | 30 | ``` |
22 | 31 | * In SST input files, GlobalParams have been renamed to SharedParams to reflect the fact that they can be shared among elements but are not "global" as there can be multiple groups of SharedParams that are not shared across all elements. |
23 | 32 | * Reminder: The Event::Handler and Clock::Handler handler types were deprecated in SST 14.0. Use Event::Handler2 and Clock::Handler2 instead. |
24 | 33 | * The Handler signatures will be switched to match Handler2 in SST 16.0. |
25 | 34 | * The name Handler2 will be deprecated at SST 16.0 and removed in SST 17.0. |
26 | | - * Update all elements to use the new signatures before or at SST 16.0. Switching before SST 16.0 will require changing (`Handler<class>` -> `Handler2<class,&class::callback_function>`) prior to SST 16.0 and then to (`Handler<class, &class::callback_function>`) after 16.0. |
| 35 | + * Update all elements to use the new signatures before or at SST 16.0. Switching before SST 16.0 will require changing (`Handler<class>` -> `Handler2<class,&class::callback_function>`) prior to SST 16.0 and then to (`Handler<class, &class::callback_function>`) after 16.0. |
27 | 36 | Waiting until SST 16.0 to switch will cause your code to break in SST 16.0 until you change the definition of (`Handler<class>` -> `Handler<class, &class::callback_function>`). |
28 | | -* SST-Macro is a maintenance-only development effort. Due to increasing divergence between the SST-Core and SST-Macro, we will no longer be ensuring that the SST-Core and SST-Macro devel branches stay in sync. |
| 37 | +* SST-Macro is a maintenance-only development effort. Due to increasing divergence between the SST-Core and SST-Macro, we will no longer be ensuring that the SST-Core and SST-Macro devel branches stay in sync. |
29 | 38 | However, we will continue to ensure that the master branches and releases of SST-Macro work with SST-Core. Where possible, we recommend using the mercury element instead of SST-Macro. |
30 | 39 | If mercury is missing key functionality present in SST-Macro that is not found elsewhere in SST-Elements, please let us know. |
31 | 40 |
|
|
0 commit comments