| commit | bcb3bd09275f833a76d1122f59d4b49b52c8d299 | [log] [tgz] |
|---|---|---|
| author | Victor Chernyakin <chernyakin.victor.j@outlook.com> | Thu Sep 04 10:32:56 2025 -0700 |
| committer | GitHub <noreply@github.com> | Thu Sep 04 10:32:56 2025 -0700 |
| tree | 9dbc13b4cc0b0c4d7bc66be615fa1091813f009b | |
| parent | bdb9283eec633585a14f7b1640822448c17ed71a [diff] |
[clang-tidy] Raise minimum standard level for several checks from C++98 to C++11 (#152401) `modernize-replace-auto-ptr`, `modernize-use-equals-delete`, and `modernize-use-auto` use `std::unique_ptr`, `= delete`, and `auto` respectively, which are all C++11 features. The interesting bit is `modernize-use-nullptr`'s tests: - Some relied on int-to-pointer conversions that were removed in C++11. There are two variations here. First, tests like this, which become ill-formed: ```cpp const int null = 0; void * ptr = null; ``` I just deleted these cases; if they're ill-formed, we're not losing anything, right? Second, tests like this: ```cpp float * ptr = (float *)int(0.f); ``` These don't become ill-formed, but start generating a different AST. In C++98, they are `NullToPointer` conversions, but in C++11, they become generic `IntegralToPointer` conversions. I deleted these cases too, though I'm less sure here. - Folded `struct Bar` into `class A`, because those both suffer from the same false negatives.
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.