Sciweavers

Share
CASES
2007
ACM

Non-transparent debugging for software-pipelined loops

8 years 8 months ago
Non-transparent debugging for software-pipelined loops
This paper tackles the problem of providing correct information about program variable values in a software-pipelined loop through a non-transparent debugging approach. Since modern processors provide instruction level parallelism, software pipelining techniques have been developed to achieve better performances, especially in the context of embedded systems. Indeed, the effectiveness of software pipelining on such systems has been demonstrated both theoretically and experimentally. As it overlaps iterations and reorders statements, it also makes standard debugging information irrelevant. Hence debugging a loop which has been software-pipelined becomes very difficult. In this paper, we propose a solution relying on selected information to be generated by the compiler and an algorithm for the debugger not to mislead the user. ACM Classification D.2.5 [Software Engineering]: Testing and Debugging General Terms Algorithms, Experimentation
Hugo Venturini, Frédéric Riss, Jean-
Added 12 Aug 2010
Updated 12 Aug 2010
Type Conference
Year 2007
Where CASES
Authors Hugo Venturini, Frédéric Riss, Jean-Claude Fernandez, Miguel Santana
Comments (0)
books