Google Git
Sign in
fuchsia / third_party / llvm-project / cd071253c70b3b37a0b9d113709ca9d49a83007e
commitcd071253c70b3b37a0b9d113709ca9d49a83007e[log] [tgz]
authorFangrui Song <i@maskray.me>Fri Mar 15 10:50:21 2024 -0700
committerGitHub <noreply@github.com>Fri Mar 15 10:50:21 2024 -0700
tree449b7d9c41db8fcfbfad6e5b651474a067888f84
parentb8db3e7c7dddaa14c314a05b92c9fa3df38734e4 [diff]
[Driver] Don't alias -mstrict-align to -mno-unaligned-access

GCC ports only supports one of the options, with -mstrict-align
preferred by newer ports. They reject adding -m[no-]unaligned-access to
newer ports that use -m[no-]strict-align.
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111555).

We should not support aliases, either. Since the behavior has been
long-time for ARM (a146a48349c965932dcf304ffb8155b25307f245), support
both forms for ARM for now but remove -m[no-]unaligned-access for
RISC-V/LoongArch (see also
https://github.com/riscv-non-isa/riscv-c-api-doc/pull/62).

While here, add TargetSpecific to ensure errors on unsupported targets
(https://reviews.llvm.org/D151590) and remove unneeded CC1 options.

Pull Request: https://github.com/llvm/llvm-project/pull/85350
10 files changed
tree: 449b7d9c41db8fcfbfad6e5b651474a067888f84
  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.