* NEWS: Update for upcoming release.
This commit is contained in:
parent
dce83a649b
commit
937011692c
1 changed files with 24 additions and 12 deletions
36
NEWS
36
NEWS
|
|
@ -10,14 +10,14 @@ New in spot 2.1.2.dev (not yet released)
|
|||
formula processed, was renamed to "ltldo --stats=%#" to free %R
|
||||
for the following feature.
|
||||
|
||||
* autfilt, dstar2tgba, ltl2tgba, ltlcross, ltldo learned to time any
|
||||
task in a more precise way thanks to %R, %[LETTER]R option. User
|
||||
or system time, for children or parent, can be measured
|
||||
separately. A typical use-case is "ltldo --stats='... %[c]R ...'
|
||||
..." to measure the time spent in the tool ran by ltldo, excluding
|
||||
that of ltldo. In all tools, the difference between %r
|
||||
(wall-clock time) and %R (process time) can also be used to detect
|
||||
unreliable measurements.
|
||||
* autfilt, dstar2tgba, ltl2tgba, ltlcross, ltldo learned to measure
|
||||
cpu-time (as opposed to wall-time) using --stats=%R. User or
|
||||
system time, for children or parent, can be measured separately by
|
||||
adding additional %[LETTER]R options. A typical use-case is
|
||||
"ltldo --stats='... %[c]R ...' ..." to measure the time spent in
|
||||
the tool ran by ltldo, excluding that of ltldo. In all tools, the
|
||||
difference between %r (wall-clock time) and %R (CPU time) can also
|
||||
be used to detect unreliable measurements.
|
||||
|
||||
Library:
|
||||
|
||||
|
|
@ -42,15 +42,21 @@ New in spot 2.1.2.dev (not yet released)
|
|||
|
||||
* scc_filter() learned to preserve state names and highlighted states.
|
||||
|
||||
* The BuDDy library has been slightly optimized: the initial setup
|
||||
of the unicity table can now be vectorized by GCC, and all calls
|
||||
to setjmp are now avoided when variable reordering is disabled
|
||||
(the default).
|
||||
|
||||
Bugs:
|
||||
|
||||
* ltl2tgba was alway using the highest settings for the LTL
|
||||
* ltl2tgba was always using the highest settings for the LTL
|
||||
simplifier, ignoring the --low and --medium options. Now
|
||||
genltl --go-theta=12 | ltl2tgba --low --any
|
||||
is instantaneous as it should be.
|
||||
|
||||
* Compression could encode '6' and '22' in the same way. This issue
|
||||
only appears when using the compression from intvcomp.hh.
|
||||
* The int-vector compression code could encode 6 and 22 in the
|
||||
same way, causing inevitable issues in our LTSmin interface.
|
||||
(This affects tests/ltsmin/modelcheck with option -z, not -Z.)
|
||||
|
||||
* str_sere() and str_utf8_sere() were not returning the same
|
||||
string that print_sere() and print_utf8_sere() would print.
|
||||
|
|
@ -63,7 +69,10 @@ New in spot 2.1.2.dev (not yet released)
|
|||
|
||||
* When the automaton_stream_parser reads an automaton from an
|
||||
already opened file descriptor, it will not close the file
|
||||
anymore.
|
||||
anymore. Before that the spot.automata() python function used to
|
||||
close a file descriptor twice when reading from a pipe, and this
|
||||
led to crashes of the 0MQ library used by Jupyter, killing the
|
||||
Python kernel.
|
||||
|
||||
* remove_fin() could produce incorrect result on incomplete
|
||||
automata tagged as weak and deterministic.
|
||||
|
|
@ -72,6 +81,9 @@ New in spot 2.1.2.dev (not yet released)
|
|||
in unexpected behaviors, because set_acceptance(0,...) used to
|
||||
set the state-based acceptance flag automatically.
|
||||
|
||||
* Some buffering issue caused syntax errors to be displayed out
|
||||
of place on the on-line translator.
|
||||
|
||||
New in spot 2.1.2 (2016-10-14)
|
||||
|
||||
Command-line tools:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue