Google Git
Sign in
llvm / llvm-project / dc4cfdbb8f9f665c1699e6289b6edfbc8d1bb443
commitdc4cfdbb8f9f665c1699e6289b6edfbc8d1bb443[log] [tgz]
authorAart Bik <ajcbik@google.com>Fri Mar 29 15:30:36 2024 -0700
committerGitHub <noreply@github.com>Fri Mar 29 15:30:36 2024 -0700
treee9b7b1e2f4b94fbd8fff68a9b947a0a110c6a151
parent038e66fe59962de121ce24ee709eca7a0783cbc4 [diff]
[mlir][sparse] provide an AoS "view" into sparse runtime support lib (#87116)

Note that even though the sparse runtime support lib always uses SoA
storage for COO storage (and provides correct codegen by means of views
into this storage), in some rare cases we need the true physical SoA
storage as a coordinate buffer. This PR provides that functionality by
means of a (costly) coordinate buffer call.

Since this is currently only used for testing/debugging by means of the
sparse_tensor.print method, this solution is acceptable. If we ever want
a performing version of this, we should truly support AoS storage of COO
in addition to the SoA used right now.
7 files changed
tree: e9b7b1e2f4b94fbd8fff68a9b947a0a110c6a151
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. libc/
  11. libclc/
  12. libcxx/
  13. libcxxabi/
  14. libunwind/
  15. lld/
  16. lldb/
  17. llvm/
  18. llvm-libgcc/
  19. mlir/
  20. openmp/
  21. polly/
  22. pstl/
  23. runtimes/
  24. third-party/
  25. utils/
  26. .clang-format
  27. .clang-tidy
  28. .git-blame-ignore-revs
  29. .gitattributes
  30. .gitignore
  31. .mailmap
  32. CODE_OF_CONDUCT.md
  33. CONTRIBUTING.md
  34. LICENSE.TXT
  35. pyproject.toml
  36. README.md
  37. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.