Difference: DTTAlgorithm (5 vs. 6)

Revision 62008-01-22 - ChenDing

Line: 1 to 1
 
META TOPICPARENT name="GccVersion4_1_0"
Changed:
<
<

Dependence Tracing Algorithm

-- TongxinBai - 21 Jan 2008
>
>

Dependence Tracing Algorithm

 
Changed:
<
<
>
>
created by TongxinBai - 21 Jan 2008

  The profiling tool is built upon a compile-time instrumentation framework and a separate tool file that contains the realizations of the instrumented functions.
Line: 87 to 87
 Field file_name and line hold the access level location of the write while field toplev_file_name and toplev_line hold the function level location.

To help record function (top) level locations, two global variables are used, toplev_file_name and toplev_line. The two variables hold the current function level location so that they can be copied to the corresponding two fields in struct _write when a write is to be recorded.

Added:
>
>

Explanations

For a function marked for detailed recording, we would like to record the dependence between any pair of its statements, even though the actual data access happens in a function call to some other functions. The function-level dependence is between two statements of a detail recorded function. The access-level dependence is between the two statements accessing the memory.

The frozen time increments only when a statement in a detail recorded function is executed. The analyzer records a dependence only when the source and the sink happen at different frozen times. It removes from consideration dependences that span an execution without any occurrence of detail recorded statements.

More notes

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback