➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2021-05-06 15:09 by skip.montanaro, last changed 2022-04-11 14:59 by admin.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 25949 | open | skip.montanaro, 2021-05-06 15:49 | |
| Messages (1) | |||
|---|---|---|---|
| msg393099 - (view) | Author: Skip Montanaro (skip.montanaro) *  |
Date: 2021-05-06 15:09 | |
When the interpreter is compiled with computed goto support, the TARGET macro is defined like this: #define TARGET(op) op: TARGET_##op If computed gotos are disabled, the implementation is simpler: #define TARGET(op) op I'm finding it useful to use those labels as gdb breakpoint targets. Is there some reason not to always define the TARGET_##op label? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:45 | admin | set | github: 88226 |
| 2021-05-06 15:49:48 | skip.montanaro | set | keywords:
+ patch stage: patch review pull_requests: + pull_request24612 |
| 2021-05-06 15:09:57 | skip.montanaro | create | |