Commit 95f1a7bb authored by Benjamin Peterson's avatar Benjamin Peterson Committed by GitHub

remove support for splitting the ceval switch into multiple switches (#4099)

This kludge is from 1992. Any C99 compiler is going to be able to handle the
ceval dispatch switch.

Anyway, we have much bigger switches than the ceval dispatch one around. (See,
e.g., Objects/unicodetype_db.h.)
parent d7ac0612
...@@ -22,9 +22,6 @@ ...@@ -22,9 +22,6 @@
#include <ctype.h> #include <ctype.h>
/* Turn this on if your compiler chokes on the big switch: */
/* #define CASE_TOO_BIG 1 */
#ifdef Py_DEBUG #ifdef Py_DEBUG
/* For debugging the interpreter: */ /* For debugging the interpreter: */
#define LLTRACE 1 /* Low-level trace feature */ #define LLTRACE 1 /* Low-level trace feature */
...@@ -1662,9 +1659,6 @@ _PyEval_EvalFrameDefault(PyFrameObject *f, int throwflag) ...@@ -1662,9 +1659,6 @@ _PyEval_EvalFrameDefault(PyFrameObject *f, int throwflag)
DISPATCH(); DISPATCH();
} }
#ifdef CASE_TOO_BIG
default: switch (opcode) {
#endif
TARGET(RAISE_VARARGS) { TARGET(RAISE_VARARGS) {
PyObject *cause = NULL, *exc = NULL; PyObject *cause = NULL, *exc = NULL;
switch (oparg) { switch (oparg) {
...@@ -3373,10 +3367,6 @@ _PyEval_EvalFrameDefault(PyFrameObject *f, int throwflag) ...@@ -3373,10 +3367,6 @@ _PyEval_EvalFrameDefault(PyFrameObject *f, int throwflag)
PyErr_SetString(PyExc_SystemError, "unknown opcode"); PyErr_SetString(PyExc_SystemError, "unknown opcode");
goto error; goto error;
#ifdef CASE_TOO_BIG
}
#endif
} /* switch */ } /* switch */
/* This should never be reached. Every opcode should end with DISPATCH() /* This should never be reached. Every opcode should end with DISPATCH()
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment