Google Git
Sign in
fuchsia / third_party / llvm-project / 09175195320cb573d5015e30b6da4e5677350364
commit09175195320cb573d5015e30b6da4e5677350364[log] [tgz]
authorMarina Taylor <marina_taylor@apple.com>Mon Mar 17 18:28:45 2025 +0000
committerMarina Taylor <marina_taylor@apple.com>Fri May 02 17:37:37 2025 +0100
treeea3310183791c595231e52adc7f6d6cf1426196e
parentee3610efb511ec0a8d5ebd2016ce23b4b4344cd1 [diff]
[AArch64] Allow the clang.arc.attachedcall marker to be optional.

Now that the clang.arc.attachedcall bundle requires having an
operand, which we emit a call to in the RVMARKER sequence,
we can achieve our real goal: make the marker NOP optional.

The intention is that a new objc runtime call will be introduced,
which doesn't require the NOP to be present, but must be adjacent
to the possibly-autorelease-returning call (that the bundle is
attached to).

This is achieved by having ISel embed whether the marker is necessary
with an additional boolean target immediate operand.

Co-authored-by: Ahmed Bougacha <ahmed@bougacha.org>
6 files changed
tree: ea3310183791c595231e52adc7f6d6cf1426196e
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libunwind/
  16. lld/
  17. lldb/
  18. llvm/
  19. llvm-libgcc/
  20. mlir/
  21. offload/
  22. openmp/
  23. polly/
  24. pstl/
  25. runtimes/
  26. third-party/
  27. utils/
  28. .clang-format
  29. .clang-format-ignore
  30. .clang-tidy
  31. .git-blame-ignore-revs
  32. .gitattributes
  33. .gitignore
  34. .mailmap
  35. CODE_OF_CONDUCT.md
  36. CONTRIBUTING.md
  37. LICENSE.TXT
  38. pyproject.toml
  39. README.md
  40. 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.