diff options
| author | Aaron Ballman <aaron@aaronballman.com> | 2025-05-01 07:08:06 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-01 07:08:06 -0400 |
| commit | 00f9ef282c7482754a0fea497417604d1deca9fa (patch) | |
| tree | b773b05b787f2c47a202e461486410c0df4024d4 /clang/unittests/Frontend/CompilerInstanceTest.cpp | |
| parent | 4b3acfb10a6b6388b95682c471bdbf42982be030 (diff) | |
| download | llvm-00f9ef282c7482754a0fea497417604d1deca9fa.zip llvm-00f9ef282c7482754a0fea497417604d1deca9fa.tar.gz llvm-00f9ef282c7482754a0fea497417604d1deca9fa.tar.bz2 | |
[C] Modify -Wdefault-const-init (#137961)
Post-commit review feedback on
https://github.com/llvm/llvm-project/pull/137166 raised a concern from
the Linux kernel about wanting to silence the new diagnostic when the
uninitialized object is a const member of a structure. These members can
be initialized later if the containing object is non-const, such as
through a call to memset, for example.
This splits the diagnostic groups into:
```
-Wc++-compat
-Wdefault-const-init
-Wdefault-const-init-field
-Wdefault-const-init-var
-Wdefault-const-init-unsafe
-Wdefault-const-init-field-unsafe
-Wdefault-const-init-var-unsafe
```
---------
Co-authored-by: Mariya Podchishchaeva <mariya.podchishchaeva@intel.com>
Diffstat (limited to 'clang/unittests/Frontend/CompilerInstanceTest.cpp')
0 files changed, 0 insertions, 0 deletions