From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 21FE53858C5E; Thu, 2 Nov 2023 15:24:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 21FE53858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698938681; bh=IY/ldS629avJT4MRoumTNz4eKxlpYIlXMyToGZGnATQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=esIyInK8MQEFoQWmuCcjq+FDpcP6wEkF2T5UTq5QUyHdeDrzRbKOXXBEGjNLTlriE CRoojYnXSoDo38g3SSAKCKgGv8dBNm0r6hhMv4w9517oT3T5GzZ7IrThG0/d23W8tx bov8Vue8ix56rMSKsf9TdFOb4fpZLXEkpJU7QVvQ= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112350] gcc is not triggering a dangling reference indicating stack use after return Date: Thu, 02 Nov 2023 15:24:40 +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: 13.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 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=3D112350 --- Comment #1 from Andrew Pinski --- With optimization enabled and without -fsanitize=3Daddress we get: : In function 'const int& foo1()': :12:18: warning: using a dangling pointer to 'x' [-Wdangling-pointe= r=3D] 12 | return s.get(); | ^ :9:9: note: 'x' declared here 9 | int x =3D 234; | ^=