You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to run shark on MacOS(Mac with M2 pro chip) with vulkan gpu, it runs into the issue:
<eval_with_key>.25:146:17: error: 'spirv.Bitcast' op result #0 must be 8/16/32/64-bit integer or 16/32/64-bit float or bool or vector of bool or 8/16/32/64-bit integer or 16/32/64-bit float values of length 2/3/4/8/16 or any SPIR-V pointer type, but got 'vector<1xf32>'
<eval_with_key>.25:146:17: note: see current operation: %119 = "spirv.Bitcast"(%114) : (vector<2xf16>) -> vector<1xf32>
The text was updated successfully, but these errors were encountered:
Ranvirsv
changed the title
failed to legalize operation 'vector.bitcast' -- Shark on MacOS(Vulkan gpu)
failed to legalize operation 'sprv.Bitcast' -- Shark on MacOS(Vulkan gpu)
Jun 3, 2023
Ranvirsv
changed the title
failed to legalize operation 'sprv.Bitcast' -- Shark on MacOS(Vulkan gpu)
failed to legalize operation 'spirv.Bitcast' -- Shark on MacOS(Vulkan gpu)
Jun 3, 2023
Ranvirsv
changed the title
failed to legalize operation 'spirv.Bitcast' -- Shark on MacOS(Vulkan gpu)
'spirv.Bitcast' op result #0 must be 8/16/32/64-bit... got a 'vector<1xf32>' -- Shark on MacOS(Vulkan gpu)
Jun 5, 2023
What happened?
Trying to run shark on MacOS(Mac with M2 pro chip) with vulkan gpu, it runs into the issue:
I have attached the error.log file
error.log
Steps to reproduce your issue
cd SHARK
Get the input mlir
Set the location for IREE_SAVE_TEMPS
export IREE_SAVE_TEMPS=/path/to/some/directory
Run the command to get the inpur mlir
python3 apps/stable_diffusion/scripts/txt2img.py -p "a photograph of an astronaut riding a horse" --save_vmfb
Compile the core-input.mlir
iree-compile-binary path\to\core-input.mlir --iree-vulkan-target-triple=m1-unknown-macos --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-hal-target-backends=vulkan -o core.vmfb 2> error.log
The text was updated successfully, but these errors were encountered: