[AArch64] Fix using NEON copies in streaming-mode-enable regions. (#174738) The current checks for if we're allowed to use a NEON copy works based on the function attributes, which works most of the time. However in one particular case where a normal function calls a streaming one, there's a window of time where we enable SM at the call site and the emit a copy for an outgoing parameter. This copy was lowered to a NEON move which is illegal. There's also another case where we could end up generating these, related to zero cycle move tuning features. Both of these cases is fixed in this patch by walking back from the copy to look for any streaming mode changes (within the current block). I know this is pretty ugly but I don't have a better solution right now. rdar://167439642
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.
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.
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.