-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fixes from Alan Dayton (Many thanks!) #1204
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
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.
Looks like there were some failures w/ the cuda pro-e intersection tests w/ our
|
std::int8_t num_nbrs[MAX_VERTS] {}; | ||
VertexNbrs nbrs[MAX_VERTS] {}; |
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.
The cuda test case passes when I revert this default member initalizer change. I am not sure why this causes problem on device...
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.
!!! Well, thank you for checking on that, Brian. That's very odd.
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.
Great catch @bmhan12 -- looks like uninitialized memory
@agcapps is this ready to be merged after pipelines pass? |
Yes, it is. |
@bmhan12 , any further comment on this MR? |
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.
@bmhan12 , any further comment on this MR?
Looks good to me!
Summary