Google Git
Sign in
llvm / llvm-project / 5f38436d34360d17b58f643650f3605bb9609a34
commit5f38436d34360d17b58f643650f3605bb9609a34[log] [tgz]
authorFangrui Song <i@maskray.me>Tue Mar 19 10:37:51 2024 -0700
committerGitHub <noreply@github.com>Tue Mar 19 10:37:51 2024 -0700
tree087eb574a7ff899fa18133ebb54833aa5257ce8b
parentb9a41b9e9b1441a7b0ca0fb95b9184f73bbfd4b5 [diff]
[Driver] -fsanitize=undefined: don't expand to signed-integer-overflow if -fwrapv (#85501)

Linux kernel uses -fwrapv to change signed integer overflows from
undefined behaviors to defined behaviors. However, the security folks
still want -fsanitize=signed-integer-overflow diagnostics. Their
intention can be expressed with -fwrapv
-fsanitize=signed-integer-overflow (#80089). This mode by default
reports recoverable errors while still making signed integer overflows
defined (most UBSan checks are recoverable by default: you get errors in
stderr, but the program is not halted).

-fsanitize=undefined -fwrapv users likely want to suppress
signed-integer-overflow, unless signed-integer-overflow is explicitly
enabled. Implement this suppression.
2 files changed
tree: 087eb574a7ff899fa18133ebb54833aa5257ce8b
  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.