Message 393099 - Python tracker

➜

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.

Author	skip.montanaro
Recipients	skip.montanaro
Date	2021-05-06.15:09:57
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1620313797.79.0.147894206255.issue44060@roundup.psfhosted.org>
In-reply-to

Content
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?

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
2021-05-06 15:09:57	skip.montanaro	set	recipients: + skip.montanaro
2021-05-06 15:09:57	skip.montanaro	set	messageid: <1620313797.79.0.147894206255.issue44060@roundup.psfhosted.org>
2021-05-06 15:09:57	skip.montanaro	link	issue44060 messages
2021-05-06 15:09:57	skip.montanaro	create