-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Build] Fails to parse FP16 LayerNormalization in opset>=18 #16341
Comments
Does your tested onnx model contains a
so fyi, in opset 18, ReduceMean introduces -ReduceMean-18: You may want to update your model if possible. |
This is the output with ONNX 1.14 or 1.13 and onnxruntime-gpu 1.15 with
It seems no issue in my machine (Ubuntu 20.04). |
Thanks for the prompt replies. @tianleiwu I can confirm this is working when I enable the CUDAExecutionProvider, so issue here is only with CPU implementation. |
Currently, cpu supports float version of LayerNormalization up to opset 17 (as in #12978). @skottmckay For opset 18/19, when there is no implement of LayerNormalization in CPU, it will use ONNX function of opset-18. That error might have same root cause as in #16438. The solution is to extend the float version of LayerNormalization in CPU EP to opset 18. |
Looks very likely so. Is there a way for ORT to select to correct decomposition there? |
Added observation in #16438 |
Describe the issue
FP16 LayerNormalization fails for opsets 18 and 19, but works for opset 17, throwing this error in session creation:
FP32 LayerNormalization is not affected.
FP16 LayerNormalization in opset 17 works as expected.
Please see a short Python script to reproduce under "Build script".
Generated with latest ONNX and ONNXRunTime releases:
pip install onnx==1.14.0 onnxruntime==1.15.0
Urgency
Required for NVIDIA project, can't share full details publicly.
Target platform
x86 Ubuntu 20.04
Build script
Error / output
Visual Studio Version
No response
GCC / Compiler Version
No response
(edited formatting)
The text was updated successfully, but these errors were encountered: