Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
Closed
Description
TheSPEC_FAIL_KIND is not displayed correctly due to not being adequately maintained.
e.g
Lines 1471 to 1482 inb1dcdef
| #ifdefPy_STATS | |
| staticint | |
| builtin_call_fail_kind(intml_flags) | |
| { | |
| switch (ml_flags& (METH_VARARGS |METH_FASTCALL |METH_NOARGS |METH_O | | |
| METH_KEYWORDS |METH_METHOD)) { | |
| caseMETH_VARARGS: | |
| returnSPEC_FAIL_CALL_PYCFUNCTION; | |
| caseMETH_VARARGS |METH_KEYWORDS: | |
| returnSPEC_FAIL_CALL_PYCFUNCTION_WITH_KEYWORDS; | |
| caseMETH_FASTCALL |METH_KEYWORDS: | |
| returnSPEC_FAIL_CALL_PYCFUNCTION_FAST_WITH_KEYWORDS; |
According to the context,METH_FASTCALL | METH_KEYWORDS flag does not cause specialization failure.
However, themethod descr fail kind will also be shown asSPEC_FAIL_CALL_PYCFUNCTION, becausebuiltin_call_fail_kind function is called incorrectly in thespecialize_method_descriptor function.
I'd like to submit a PR to fix them and make them display correctly.