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 2E796385800E; Thu, 31 Mar 2022 09:25:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E796385800E
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/105108] incomplete/incorrect DWARF information at -O1 and
 -Og after inlining a function returning a constant
Date: Thu, 31 Mar 2022 09:25:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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-105108-4-BTl2f1FZfJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105108-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2022 09:25:24 -0000

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And I certainly can't reproduce the wrong-debug issue you're talking about.
If I change it to char l_144 =3D 8;
then optimized dump has:
  <bb 2> [local count: 1073741824]:
  # DEBUG BEGIN_STMT
  # DEBUG l_144 =3D> 8
  # DEBUG BEGIN_STMT
  # DEBUG l_165 =3D> 128
  # DEBUG BEGIN_STMT
  # DEBUG l_144 =3D> NULL
  # DEBUG BEGIN_STMT
  a =3D 1;
  return 0;
and in the debugger it correctly says that
(gdb) p l_144
$1 =3D <optimized out>
because at the a =3D 1 store the value is unknown.=