[Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan

2022-10-28 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 --- Comment #5 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:3f9c071324eff249b23a7531e447fc17d928 commit r13-3539-g3f9c071324eff249b23a7531e447fc17d928 Author: Martin Liska Date:

[Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan

2022-10-19 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 --- Comment #4 from Martin Liška --- > Is there some documentation explaining this, or telling Sanitizer > users to turn off warnings-as-errors? Unfortunately, it is not, but we should include it. Generally speaking, -Wmaybe-uninitialized is

[Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan

2022-10-18 Thread jzwinck at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 --- Comment #3 from John Zwinck --- Martin, this bug is the only false positive I see in a large corporate codebase. I think your comment makes it sound like this is a documented thing where there are tons of false positives and it's not

[Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan

2022-10-17 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 --- Comment #2 from Martin Liška --- I mean warnings that are false-positives.

[Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan

2022-10-17 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 Martin Liška changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED