Open marty1885 opened 2 hours ago
Looks similar to https://github.com/tenstorrent/tt-metal/issues/15032
@marty1885 could you pass last parameter multicore=true to the tilize_with_zero_padding please?
@dmakoviichuk-tt The problem is not tilize_with_zero_padding
. It's with ttnn::reshape
. The line Original shape: ttnn.Shape([1, 1, 1[32], 65536])
is printed. I assume this means tilize_with_zero_padding passes?
You are right. The problem is indeed in tilize_with_zero_padding.
Update: No,with multicore=true
i get the same error.
ah :( thats sad. btw I've got second idea to make it work. Out of curiosity (we still need to fix this one )Is it possible to reshape before tilize?
@dmakoviichuk-tt No unfortunately. ttnn::reshape
eventually calls ttnn::to_layout
and runs into the same issue.
Describe the bug I'm attempting to eliminate most if not all CPU fallback code paths in my GGML backend. One of which is reshaping a single vector into a 3D tensor - I know this is not efficient on TT hardware and I should eliminate it completely by graph rewrite in the future - This operation fails when performed purely on device.
To Reproduce The following is the minimal reproducible example. Compile and run it:
Observe the error:
Expected behavior Reshape from 1D vector should work no matter the vector size. Or at least the API/document should provide some way to indicate the algorithm cannot run if the input exceeds a certain size.
Screenshots If applicable, add screenshots to help explain your problem.
Please complete the following environment information:
Additional context Add any other context about the problem here.