The tick profiler works by interrupting the Prolog code every so often and checking at each point the code was. More...

Detailed Description

The tick profiler works by interrupting the Prolog code every so often and checking at each point the code was.

The profiler must be able to retrace the state of the abstract machine at every moment The major advantage of this approach is that it gives the actual amount of time being spent per procedure, or whether garbage collection dominates execution time The major drawback is that tracking down the state of the abstract machine may take significant time, and in the worst case may slow down the whole execution

The following procedures are available:

profinit

Initialise the data-structures for the profiler Unnecessary for dynamic profiler

profon

Start profiling

profoff

Stop profiling

Macro Definition Documentation

◆ CONTEXT_BP

#define CONTEXT_BP ( scv ) NULL

Definition at line 142 of file gprof.c.

◆ CONTEXT_PC

#define CONTEXT_PC ( scv ) NULL

Definition at line 141 of file gprof.c.

Function Documentation

◆ Yap_InitLowProf()

void Yap_InitLowProf ( void )

Definition at line 1202 of file gprof.c.

Macros
#define	CONTEXT_PC(scv) NULL

#define	CONTEXT_BP(scv) NULL

Functions
void	Yap_InitLowProf (void)