-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix compiler error in ASLocking #trivial #1079
Fix compiler error in ASLocking #trivial #1079
Conversation
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!
45e9cbb
to
af032b5
Compare
🚫 CI failed with log |
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 don't think this is correct – if we don't initialize the variable it will contain garbage values. What's the specific compiler error we see?
Good point, updated the diff. The compiler complaints about missing initialization for the lock set’s locks array (i.e locks.locks). |
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.
Good deal. I think that {0}
is only valid for multi-member structs in C++. In C it may not be well-defined. Do we not also use that construct in ASPendingState?
Looks like we do, but the engineer who's working on this project hasn't hit it yet (and I heard it's non-trivial for me to apply all of her changes). Will follow-up if need to. |
Thanks btw! |
Hitting this error because we're compiling with a stricter set of build rules internally.