[BUGFIX ]'AttributeError: '_OpNamespace' '_C' object has no attribute 'silu_and_mul_nvfp4_quant'

[JartX]

The PR fixes the bug introduced in PR: #23671 and reported in #23916 of inference in ROCM, it only checks if the attribute exists before calling the function

[gemini-code-assist]

Code Review

This pull request addresses a bug that causes a crash on ROCM platforms by adding a check for the existence of the silu_and_mul_nvfp4_quant operator before it's used. This operator is specific to NVIDIA hardware and not available on ROCM, so adding a hasattr check is the correct way to prevent an AttributeError during the compilation's FixFunctionalizationPass. The change is correct, minimal, and effectively resolves the reported issue, improving the codebase's cross-platform compatibility.

[JartX]

@elvischenv Please check this out if you're so kind :)

[JartX]

@jeejeelee please check it, I think my solution could be improved by filtering directly by ROCM, but I would need to test it on AITER hardware, which I do not have.

[elvischenv]

Thanks for reporting this.

Previously #10867 added torch.ops._C.silu_and_mul_quant.default(silu_and_mul + FP8 quant fusion) which should be also only available on cuda. However, that PR didn't exclude the op from ROCM arch like my PR did. My PR originally excluded torch.ops._C.silu_and_mul_nvfp4_quant.default(silu_and_mul + NVFP4 quant fusion) so that triggered this issue.

We may also need to exclude torch.ops._C.silu_and_mul_quant.default from ROCM in csrc/ops.h and csrc/torch_bindings.cpp, and maybe come up with a way to exclude these op from the common path fix_functionalization.py(like this PR did?).

@SageMoore @ProExpertProg may have comments

[JartX]

Good @elvischenv, thank you for the speed and cooperation, just checking if the attribute is available, and then calling the function

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @JartX.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork