From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 91CBD385782C; Wed, 19 Oct 2022 07:19:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 91CBD385782C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666163959; bh=SZ4NTFUN5fT7yp8SrnIIz+47nrJbL0cRjOXdDq1BBak=; h=From:To:Subject:Date:In-Reply-To:References:From; b=r2LMtMlgwjzRSHHWFViUdyxXsneybWKO16gRs0PBjtVvzbN8o1Epmko+dHQrxI8xj 7ghAgUMbOGb4m6O5TVRBU4kQQ3qAR4rYUVwq3kT33+2NyTwXnLEPLDgKnuW3uWpT4N DMEpNBbE6wl/vGLT0E/g6RSiDqj8XUQ63Uq5RJQw= From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan Date: Wed, 19 Oct 2022 07:19:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107298 --- Comment #4 from Martin Li=C5=A1ka --- > 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 a warning with a pretty high false-positive rate. And it's known that sanitizers tend to introduce new warnings which are false positives. Anyway, let me update the documentation= .=