Skip to content

Conversation

@jeffbolznv
Copy link
Collaborator

Fixes #10434

Removing the break and putting if tests right around the loads was an optimization, but the max() operation also needed the if test.

@jeffbolznv jeffbolznv requested a review from 0cc4m November 20, 2024 19:25
@stduhpf
Copy link
Contributor

stduhpf commented Nov 20, 2024

It does fix the issue. Thank you!

Copy link
Collaborator

@0cc4m 0cc4m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The unit tests didn't catch this one. Thanks for the quick fix.

@0cc4m 0cc4m merged commit 9abe9ee into ggml-org:master Nov 20, 2024
7 checks passed
@jeffbolznv
Copy link
Collaborator Author

Yeah, I guess this requires a value larger than the max being computed for an invalid column, and the random data in the unit tests just isn't likely to generate that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Garbage outputs on Vulkan backend since #10301 (possible NaN issue?)

3 participants