-
Notifications
You must be signed in to change notification settings - Fork 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
Different output between CPU and Metal with the im2col operator #931
Comments
Do the |
all passed with one failed with
|
The @JohannesGaessler was asking for the result from make -j && ./bin//test-backend-ops -o IM2COL
@lovemefan Try to add a test to |
The script can pass, but I can’t reproduce my bug in add a examples in test-backend-ops. I spent some time troubleshooting, but couldn’t find anything.
in my code, I noticed the output tensor looks like random data.
when set dst type
what can I do to provide more information next? |
This bug is the same as #991, but occurring with Metal |
fixed in (llama/9943) |
In the code of my custom model, during debugging, I noticed that the im2col operator produces different results on Metal compared to the CPU.
my device is M1 pro.
code at https://github.com/lovemefan/SenseVoice.cpp/blob/1dfa60459a0104a68066ddf7c275f4c0a33972a6/sense-voice/csrc/sense-voice-encoder.cc#L267-L269
here is my callback log of tensor, the im2col's name is node55
cpu.log
metal.log
I would appreciate your help with this. Thank you!
The text was updated successfully, but these errors were encountered: