cpu: aarch64: Expand brgemm aarch64 unsupported cases handling mechanism

[Radu2k]

Remove the asserts that cause segfaults in the test and handle unsupported cases based on oneDNN status type. As well remove the forgotten asserts in brgemm_matmul.cpp and modify acl_deconvolution.hpp to make op/f32/deconv_bwd_d test pass.

Description

This replaces the asserts in brgemm that make test_benchdnn_modeC_graph_ci_cpu segfault on AArch64 by replacing the asserts with status_t type in oneDNN. As well, the segfault of --graph --skip-impl=ref --case=op/f32/deconv.json test when built with gcc-10 and g++-10, which is part of the graph test batch.

Checklist

General

• Do all unit and benchdnn tests (make test and make test_benchdnn_*) pass locally for each commit?
• Have you formatted the code using clang-format?

Bug fixes

• Have you included information on how to reproduce the issue (either in a github issue or in this PR)?
• Have you added relevant regression tests?

[dzarukin]

Why is this change needed? What's the issue with auto?

[Radu2k]

@dzarukin Hi Dmitry, thanks for having a look into this. I have replaced auto with explicit data types for improved readability, consistency, and type safety. When debugging it was particularly useful to have the data type specified and I did go an extra mile checking that the function returns the same type. Should not be a problem but I am happy to review it if it is a deal breaker.

[Radu2k]

I’ve been working on this the past few days, and all tests for the Graph API should run fine. There are a few edge cases that fail but I’ll detail in an issue soon and shall be fixed in the foreseeable future.

Thanks for the approval!

[mgouicem]

Could you split the change to acl_deconvolution in a separate commit as it seems to fix a different issue (unrelated to brgemm)?

[Radu2k]

@mgouicem Hi Mourad, thanks for having a look into this. I understand your opinion but why I have added it to this PR is because --graph --skip-impl=ref --case=op/f32/deconv.json is part of test_benchdnn_modeC_graph_ci_cpu batch apparently, so it is a direct fix of the test. That being said it is the only place where we have spotted the problem.