view Python/pyfpe.c @ 31487:f57f5ce22c8d legacy-trunk

SF patch #884022: dynamic execution profiling vs opcode prediction (Contributed by Andrew I MacIntyre.) disables opcode prediction when dynamic execution profiling is in effect, so the profiling counters at the top of the main interpreter loop in eval_frame() are updated for each opcode.
author Raymond Hettinger <python@rcn.com>
date Sun, 08 Feb 2004 19:59:27 +0000
parents 2dea40e40d9d
children
line wrap: on
line source

#include "pyconfig.h"
#include "pyfpe.h"
/* 
 * The signal handler for SIGFPE is actually declared in an external
 * module fpectl, or as preferred by the user.  These variable
 * definitions are required in order to compile Python without
 * getting missing externals, but to actually handle SIGFPE requires
 * defining a handler and enabling generation of SIGFPE.
 */

#ifdef WANT_SIGFPE_HANDLER
jmp_buf PyFPE_jbuf;
int PyFPE_counter = 0;
#endif

/* Have this outside the above #ifdef, since some picky ANSI compilers issue a 
   warning when compiling an empty file. */

double
PyFPE_dummy(void *dummy)
{
	return 1.0;
}