-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
🚧 Planner flag optimizations #4433
base: MK3
Are you sure you want to change the base?
Conversation
All values in bytes. Δ Delta to base
|
@@ -233,7 +235,7 @@ FORCE_INLINE block_t *plan_get_current_block() | |||
return(NULL); | |||
} | |||
block_t *block = &block_buffer[block_buffer_tail]; | |||
block->busy = true; |
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.
Note this is called in the Stepper ISR. Is it safe to drop the volatile
keyword?
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 worry about race conditions here
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 think yes. I didn't see any place where volatile was really needed.
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.
Added @wavexx as reviewer, I think he would know best if this is OK.
Combined boolean variables in the planner struct with the "flag" variable