baidu / baidu/babylon

Remove some suppress of -Wmaybe-uninitialized after gcc fix false positive issue

Open
#68 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
653
Forks
101
PR merge metrics
No merged PRs in 30d

Description

### Minimal Reproduction
```c++
#include
#include

int main() {
::std::string str;
::std::regex re(str);
return 0;
}
```
`g++ -Werror=maybe-uninitialized -O1 -fsanitize=address`
https://godbolt.org/z/jvrdhezen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105616

### Known Defective Versions (up to 2024-10-24)
| GCC-14 | 14.1 :x: | 14.2 :x: | | |
|---------|-------------------------|-------------------------|--------------------------|-------------------------|
| GCC-13 | 13.1 :x: | 13.2 :x: | 13.3 :x: | |
| GCC-12 | 12.1 :x: | 12.2 :x: | 12.3 :x: | 12.4 :x: |
| GCC-11 | 11.1 :white_check_mark: | 11.2 :white_check_mark: | 11.3 :white_check_mark: | 11.4 :white_check_mark: |

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the project's suppressions for -Wmaybe-uninitialized, then compare them with the GCC false-positive report linked in the issue. Reproduce the warning with the provided C++ example and compiler flags; done means the obsolete suppressions are removed while the affected build still passes with the warning treated as an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.