Ukernels: mmt4d paths for arm64 fp16 extensions (#14490)

On the arm64 architecture, widely-available `fp16` and `fp16fml`
extensions allow greatly speeding up the `f16f16f16` and `f16f16f32`
cases respectively.

Along the way, this renames `fullfp16` -> `fp16` --- we follow LLVM's
nomenclature for ISA extensions and there is some confusion there as
both strings exist in LLVM, but from actually exercising this, it
appears that `fp16` is what we need here, and that conveniently allows
dropping those 4 characters, `full`.

Also along the way, reported and worked around
https://github.com/llvm/llvm-project/issues/64104

Results from `mmt4d_benchmark`, Gflop/s, single thread. Results with
these new code paths are **in bold** and are to be compared to the
results immediately above them (same element types, not using the new
code path).

benchmark | Arm Cortex-X2 | Arm Cortex-A510
--- | --- | ---
BM_mmt4d_f16f16f32_tile_8x8x1 | 47.1 | 9.5
BM_mmt4d_f16f16f32_tile_8x8x1_fp16fml | **92.0** | **12.1**
BM_mmt4d_f16f16f16_tile_8x8x1 | 46.8 | 9.49
BM_mmt4d_f16f16f16_tile_8x8x1_fp16 | **178.5** | **21.3**
12 files changed
tree: 47c9b91369970d40098408f124ad2e4bfcbbbae9
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .git-blame-ignore-revs
  22. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. README.md
  33. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.