Repository navigation
Define TARGET macro the same even when computed goto support is not enabled #88226
Description
| BPO | 44060 |
|---|---|
| Nosy | @smontanaro |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-05-06.15:09:57.774>
labels = ['interpreter-core', 'type-feature', '3.11']
title = 'Define TARGET macro the same even when computed goto support is not enabled'
updated_at = <Date 2021-05-06.15:49:48.011>
user = 'https://github.com/smontanaro'bugs.python.org fields:
activity = <Date 2021-05-06.15:49:48.011>
actor = 'skip.montanaro'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-05-06.15:09:57.774>
creator = 'skip.montanaro'
dependencies = []
files = []
hgrepos = []
issue_num = 44060
keywords = ['patch']
message_count = 1.0
messages = ['393099']
nosy_count = 1.0
nosy_names = ['skip.montanaro']
pr_nums = ['25949']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44060'
versions = ['Python 3.11']
Activity
smontanaro commentedon May 6, 2021
When the interpreter is compiled with computed goto support, the TARGET macro is defined like this:
If computed gotos are disabled, the implementation is simpler:
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?
gh-88226: Emit TARGET labels in Python/ceval.c when debugging, even i…