Issue434

Title Preprocessor: sort each block of a DTG also according to operator number
Priority bug Status resolved
Superseder Nosy List florian, gabi, malte, silvan
Assigned To Keywords
Optional summary

Created on 2014-04-23.10:35:02 by silvan, last changed by gabi.

Messages
msg4670 (view) Author: gabi Date: 2015-10-26.14:34:52
Moving DTG creation to the search component is the topic of issue549, so I close
this one.
msg3145 (view) Author: malte Date: 2014-04-25.16:46:25
This is part of the larger issue26, and it would probably make sense to split
this part off the issue into a separate one. Anyone interested in looking into this?
msg3144 (view) Author: silvan Date: 2014-04-25.16:37:58
Okay, so we close this one? Is there an issue for the work you mention which we
could link to?
msg3143 (view) Author: malte Date: 2014-04-25.11:53:27
From the title of the issue, I assume you mean transitions in the DTGs?

We're planning to get rid of the DTGs in the preprocessor output anyway and have
done most of the work in this direction already. Can I suggest we do this
instead? I don't think it should be much work (or at least it shouldn't be much
work to find out whether or not it is much work ;-)).
msg3138 (view) Author: silvan Date: 2014-04-23.10:35:02
I recently found that the output generated by the preprocessor differs when
using binaries from different machines, i.e. it is not deterministic. After
having a look at the code with Florian, we believe that transitions should also
be sorted according to their operator number, rather than according to the
operator cost. In the example we looked at, sorting only according to transition
target and condition size (and operator cost) was not a criterion which produced
a unique result.
History
Date User Action Args
2015-10-26 14:34:52gabisetstatus: chatting -> resolved
nosy: + gabi
messages: + msg4670
2014-04-25 16:46:25maltesetmessages: + msg3145
2014-04-25 16:37:58silvansetmessages: + msg3144
2014-04-25 11:53:27maltesetmessages: + msg3143
2014-04-23 10:35:02silvancreate