-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
GH-99104: Update headers for bytecodes.c and generate_cases.py #99112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Also tweak the labels near the end of bytecodes.c.
// Note that there is some dummy C code at the top and bottom of the file | ||
// to fool text editors like VS Code into believing this is valid C code. | ||
// The actual instruction definitions start at // BEGIN BYTECODES //. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: It's really the top and middle of this file. Might be worth mentioning the // Families go below this point //
section, too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to leave finding that as an exercise for the reader, since that is work in progress. The generator currently doesn't actually see the families because it stops reading after // END BYTECODES //
-- I was planning to fix that once families are actually used for anything.
resume_with_error: | ||
start_frame: | ||
unbound_local_error: | ||
; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this semicolon really needed? My IDE (VS Code) doesn't complain...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's an error to real C compilers, so better safe than sorry.
That's weird. Does the test runner really return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea about the test runner. I'll try just restarting it.
// Note that there is some dummy C code at the top and bottom of the file | ||
// to fool text editors like VS Code into believing this is valid C code. | ||
// The actual instruction definitions start at // BEGIN BYTECODES //. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to leave finding that as an exercise for the reader, since that is work in progress. The generator currently doesn't actually see the families because it stops reading after // END BYTECODES //
-- I was planning to fix that once families are actually used for anything.
resume_with_error: | ||
start_frame: | ||
unbound_local_error: | ||
; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's an error to real C compilers, so better safe than sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Also tweak the labels near the end of bytecodes.c.
This is also part of GH-98831.