From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 421333858C2C; Fri, 26 May 2023 20:21:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 421333858C2C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685132511; bh=r0UyWC/HkvFvEwYZYKLCPO9jX7wUcfCY25Qr2k2GFBM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kGSisvY5oFUJAOc9G3Wrc01Hxj+ft/PdoKENXxbv3MIMCszujWNbsHV4o8w4J61hl ftVhdika5QU6aTjQ5v+Ne+WH/xuiyzaFvpd4YiMUirYhYQIOW/BOwi8RE/9JagN4IF FDLHFbyFSxGzyIR10uj9370422LtZAeJTQ28VwAc= From: "igkper at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109991] stack-use-after-scope Date: Fri, 26 May 2023 20:21:50 +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: 14.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: igkper at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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=3D109991 --- Comment #5 from igk --- OK, becoming clearer, thanks. I'm just hoping for this to be diagnosed in s= ome way. IIUC basically GCC doesn't diagnose the UB so it proceeds with constex= pr eval just because it can, or so it thinks, and in the process makes it impossible for sanitizer to catch anything. Assuming that gets fixed some d= ay, then GCC might as well diagnose the issue itself and hence no need for sanitizer to do anything.=