[Good First Issue] [ARM]: Implement CPU plugin just-in-time emitter for Erf operation

[a-sidorova]

Context

JIT Emitters are part of code generation feature (a.k.a. tensor compiler) that automatically produces highly-efficient optimized fused subgraph binary code. Each emitter implements specific operation from low level OpenVINO dialect.

Prerequisites

Recommended to use ARM CPU based platform for development (e.g. Mac, Raspberry Pi etc). Emulators (e.g. QEMU) is still an option, but not that convenient, especially for final performance evaluation.

What needs to be done?

• Create fp32 Erf operation JIT emitter for ARM64 SIMD platform. Use OpenVINO CPU plugin JIT emitters documentation and Arm A-profile A64 Instruction Set Architecture documentation for details.
• Modify ARM64 executor and ARM64 kernel (in both places: create_eltwise_emitter and get_supported_precisions) to apply developed JIT emitter.

Before emitter implementation, please, modify tests to be sure that developed functionality is covered by test:

• Add jit kernel check in activation test, the test must fail.
• If test doesn't fail then add supported operation in CPU activation test instantiation if it's absent.

Tests

Tests are disabled in default build, so ensure to add -DENABLE_TESTS=ON into cmake command.

GoogleTest is used for testing. CPU functional test target is ov_cpu_func_tests. You can use GoogleTest filter:

./bin/[platform]/[build_type]/ov_cpu_func_tests --gtest_filter="*smoke*Activation*Erf*"

Example Pull Requests

• Abs operation: [CPU] [ARM64] jit abs #23692
• Sigmoid operation, which reuses Exp emitter: [CPU] [ARM64] jit sigmoid #23065

Resources

• Contribution guide - start here!
• What is OpenVINO?
• CPU plugin JIT emitters
• Blog post on contributing to OpenVINO
• User documentation
• Intel DevHub Discord channel - engage in discussions, ask questions and talk to OpenVINO developers
• How to link your Pull Request to an issue

Contact points

@a-sidorova, @dmitry-gorokhov

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[geeky33]

.take

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[VectorNd]

.take

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[github-actions]

Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue.

[mlukasze]

hey @VectorNd how things going? Do you need any help?