| commit | a0fcb50bf99d1d48458ee27ca92e5cd54e9910d5 | [log] [tgz] |
|---|---|---|
| author | Jon Roelofs <jonathan_roelofs@apple.com> | Fri Jul 11 10:21:13 2025 -0700 |
| committer | GitHub <noreply@github.com> | Fri Jul 11 10:21:13 2025 -0700 |
| tree | 6c2134587eb1b4adcb98b9711d0569fe49290588 | |
| parent | df10df8b0caec9e649dd8c4415610038b7926060 [diff] |
[ARM] Improve arm_neon.h header diagnostic when included on unsupported targets (#147817) The footgun here was that the preprocessor diagnostic that looks for __ARM_FP would fire when included on targets like x86_64, but the suggestion it gives in that case is totally bogus. Avoid giving bad advice, by first checking whether we're being built for an appropriate target, and only then do the soft-fp check. rdar://155449666
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.