Project

General

Profile

Feature #1880

using MSC Timing Constraints for Scheduling Synthesis

Added by Anonymous almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
12/19/2013
Due date:
% Done:

100%

Estimated time:

AF3-Project2.af3_23 (36 KB) AF3-Project2.af3_23 Anonymous, 07/07/2014 03:12 PM

Related issues

Related to Bug #1900: use of MSC timing constraints for scheduling synthesis mistakenly computes time for strongly causal componentsClosed01/23/2014

History

#1 Updated by Anonymous almost 7 years ago

  • Target version set to Phoenix 2.5 Release

#2 Updated by Anonymous almost 7 years ago

  • Status changed from In Progress to Closed
  • Assignee changed from Anonymous to Anonymous
  • Target version changed from Phoenix 2.5 Release to Phoenix 2.5 (RC1 - Feature Freeze)
  • % Done changed from 80 to 100

#3 Updated by Anonymous almost 7 years ago

  • Status changed from Closed to Resolved

#4 Updated by Anonymous almost 7 years ago

  • Target version changed from Phoenix 2.5 (RC1 - Feature Freeze) to Phoenix - BACKLOG

Discussing the feature with Sebi, we get aware we can put more into it: right now it just takes into account the time information along one logical tick, instead of using a possible complete execution path that we could obtain from the model checking of the MSC.

#5 Updated by Anonymous almost 7 years ago

  • Status changed from Resolved to In Progress
  • % Done changed from 100 to 50

#6 Updated by Anonymous over 6 years ago

  • Assignee changed from Anonymous to Anonymous

#7 Updated by Anonymous over 6 years ago

  • Target version changed from Phoenix - BACKLOG to Phoenix 2.6 Release

#8 Updated by Anonymous over 6 years ago

  • Target version changed from Phoenix 2.6 Release to AF3 2.6 RC1 Feature Freeze

#9 Updated by Anonymous over 6 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Anonymous to Anonymous
  • % Done changed from 50 to 100

#10 Updated by Anonymous over 6 years ago

Non-working model

#11 Updated by Anonymous over 6 years ago

  • Status changed from Resolved to In Progress
  • Assignee changed from Anonymous to Anonymous
  • Target version changed from AF3 2.6 RC1 Feature Freeze to Phoenix 2.7 Release

#12 Updated by Anonymous almost 6 years ago

  • Target version changed from Phoenix 2.7 Release to AF3 2.7 RC1 (features frozen)

#13 Updated by Anonymous almost 6 years ago

  • Target version changed from AF3 2.7 RC1 (features frozen) to AF3 2.7 RC4 (bugs fixed)

#14 Updated by Anonymous over 5 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF