-
Alexander Diewald authored
* Marking all Components as strongly causal would create non-realistic test cases for scheduling problems. * Heuristically mark one component of each strongly connected cycle of each component architecture as strongly causal. This eliminates most cycles. To be safe, the weak cycle checker is executed afterwards and all violating components are marked as strongly causal, too, at the risk of marking few more components as strongly causal than needed. Issue-Ref: 4008 Issue-Url: https://af3-developer.fortiss.org/issues/4008 Signed-off-by: Alexander Diewald <diewald@fortiss.org>
80c8b94b