From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C12BA3858D34; Sat, 30 Mar 2024 17:50:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C12BA3858D34
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1711821048;
	bh=UcAMF0HzrzMXQ9/neqWnzCFbm4ginlKYRbAz/lSwEDM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VQ47aEfvfiXFcLQ1p1M0l3b26Kdud3+6BfhBIEo9wG4e6hEY5L+I6qj5bq/4Q91k3
	 shpBoAWEx8zx0yGcq6vYWUgmwiydnK4b//tIkY44KRIz32tni8GkonWmyR5CgbRwiv
	 SwpOcaJ1O0nmY8wX+JrAn02oOaotNAi7gZCHG5zA=
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66487] sanitizer/warnings for lifetime DSE
Date: Sat, 30 Mar 2024 17:50:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
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: <bug-66487-4-Cz7jIajQMt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66487-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66487-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66487

--- Comment #30 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #29)
> (In reply to Alexander Monakov from comment #28)
> > The bug is about the issue of lacking diagnostics, it should be fine to=
 make
> > note of various approaches to remedy the problem in one bug report.
> >=20
>=20
> OK, well, in this case, I'd like to make this the bug report for MSan
> support in general, too, then; it's documented here:
> https://github.com/google/sanitizers/wiki/MemorySanitizer

...see also this wiki page, since GCC supports building with libc++ now:
https://github.com/google/sanitizers/wiki/MemorySanitizerLibcxxHowTo
...although, be aware that it's outdated, as per this issue:=20
https://github.com/google/sanitizers/issues/1685=