2001
DOI: 10.1007/s100090100044
|View full text |Cite
|
Sign up to set email alerts
|

System design of a CC-NUMA multiprocessor architecture using formal specification, model-checking, co-simulation, and test generation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

2011
2011
2018
2018

Publication Types

Select...
7
1

Relationship

1
7

Authors

Journals

citations
Cited by 22 publications
(13 citation statements)
references
References 22 publications
0
13
0
Order By: Relevance
“…We plan to continue our work by applying equivalence checking and model checking techniques to industrial GALS systems described in GRL. Hardware/software co-simulation is also possible using the EXEC/CAESAR framework [14] of CADP, which enables the C code generated from a GRL description to be integrated with a physical platform. We also plan to investigate the connection of GRL to verification frameworks based on the synchronous paradigm to analyse the behaviour of individual blocks corresponding to synchronous subsystems.…”
Section: Discussionmentioning
confidence: 99%
“…We plan to continue our work by applying equivalence checking and model checking techniques to industrial GALS systems described in GRL. Hardware/software co-simulation is also possible using the EXEC/CAESAR framework [14] of CADP, which enables the C code generated from a GRL description to be integrated with a physical platform. We also plan to investigate the connection of GRL to verification frameworks based on the synchronous paradigm to analyse the behaviour of individual blocks corresponding to synchronous subsystems.…”
Section: Discussionmentioning
confidence: 99%
“…Finally, we will be able to develop a stand-alone compiler to generate a prototype distributed implementation of an LNT composition of tasks, as a family of remote task and protocol processes. The code for each task could be obtained by extending the EXEC/CAESAR framework [13] of CADP (which currently generates sequential code simulating a concurrent or sequential process) to make it fit the synchronization protocol interface.…”
Section: Discussionmentioning
confidence: 99%
“…Figure 3 gives an overview of how DLC proceeds to generate a distributed implementation. DLC relies on the EXEC/CAESAR [9] tool of CADP to obtain a sequential implementation (in C) of each task process. However, the implementation produced by EXEC/CAESAR is not complete: it can list the currently possible actions of a process, but does not decide which action shall be realized.…”
Section: Environment Interaction With Hook Functionsmentioning
confidence: 99%
“…Implementation Correctness. The sequential implementation of each task is obtained by the existing EXEC/CAESAR tool of CADP, which has already been employed in a formal context [9]. Interaction between tasks is achieved by a synchronization protocol [6] that we verified [4] using a formal approach that detected possible deadlocks in other protocols of the literature [5].…”
Section: Overview Of Compilation Internalsmentioning
confidence: 99%